I suggest that you do a forum search for Azureus and timeout as it has a habit of using non standard ports whilst connecting to the internet, like using the SMTP port (25). This triggers the Internet Mail provider to scan it and because the content doesn't comply to email protocol (because it isn't an email) it often timesout.
Hihi you beat me for a second there with your reply... Anyway so basically what you are saying is that Azureus is crap just because javaw.exe is creating timeouts in avast(BTW i'm not an avast user so i have no such problems)?
There you go again, either putting words into my mouth or trying to read my mind, I didn't say it was useless, I don't swear on the forums as there have been minors on the forums. Since you aren't an avast user I would have to ask why you are hanging around the avast forums? I don't know why anyone who isn't using avast would wish to participate in the avast forums.
I wonder why it's the most popular bittorrent client out there then(millions of users)...Also not every person running azureus and avast is having problems with timeouts just a small minority(i know Sasha doesn't have these problems).And could you stop saying azureus uses non standard ports(especially since you don't know the first thing about this program since you never used it) cause it's not true.Azureus uses only one port David and that's the one that the user sets up OK.There is something going on with javaw.exe and you are basically just guessing here why these timeouts are happening(so am i) nothing else...
Not guessing, did you do a forums search as I suggested, because there are many occurances of this javaw.exe and timeouts and they are all using Azureus, coincidence, I don't know we can only go on what is presented? None of the posts in the forums that has had this javaw.exe related timeout if they havn't been using Azureus.
We need alwil here to tell us more about this issue since it's avast that is popping up these messages right(and i know this issue has been around for some time but nobody from alwil has commented on this, correct me if i am wrong)?
They may well comment, but the I believe reason the timeout occurs is something, javaw.exe is using a port monitored by the email scanner and it isn't using the email protocol, which the email scanner is expecting. Why it should be using an email port and what would initiate the call to javaw.exe to connect is the question?
Perhaps it is a coincidence that when this happens Azureus is installed also and obviously Sun's Java, could there be some spyware/malware using javaw.exe to connect? If that was the case then why would it not effect more of those not using Azureus but have Sun's Java installed?
Could it be that those experiencing this timeout with javaw.exe and have Azureus installed have an old version of Java? However, why would others with old versions of Sun's Java not be reporting this same problem.
