I have a download hung at 100% completion right now. I'm using 4.9.2. I thought you said you'd fixed this!! argh |
The beta (4.9.2) just died on me. It shows one green and four red bars and this won't change. If I tell it to disconnect it goes to five red bars. If I tell it to connect again only the first bar turns green. Search doesn't work, etc. It's been this way for half an hour now. Other network stuff works fine -- web browser for instance (where dya think this came from?). No firewall, and I didn't change any settings (firewall-related or otherwise) in limewire. It had been downloading merrily, and just became like this sometime while I was working on other things. Why would it just stop working like that? |
This just happened to me using the latest beta 4.9.4 -- Limewire dropped all four connections and refused to regenerate them. Every other network-using application continued to function normally -- web browser, etc -- and there had been no change to firewall/proxy/etc. settings (home broadband, so it wasn't someone else monkeying with the settings and disabling non-HTTP traffic or something). There is no proxy. There is a software firewall but it is instructed to leave limewire's traffic alone, and it hasn't been touched since when 4.9.4 was working normally. This has happened several times with all of the beta 4.9 series -- restarting Limewire seems to be the only recourse once this happens. Since restarting Limewire without touching anything else (firewall, rebooting Windows, whatnot) fixes the problem, it seems to be internal to Limewire. Stderr console during one such incident with 4.9.4 shows a bunch of lines like this: Code: 15-Jul-2005 8:50:07 PM com.limegroup.gnutella.ConnectionWatchdog$DudChecker run |
What operating system are you using, and how are you starting LimeWire? |
Were you using the computer at the time this happened, or did you away and just find limewire without any connections when you returned? Also, did you try clicking Disconnect and then Connect? |
Operating system: XP home. Starting limewire: C:\WINDOWS\system32\java.exe -Xmx255m -jar "C:\Program Files\LimeWire\LimeWire.jar" (It really does seem to work better given that much mem) Disconnect and then tell it to reconnect: as the other people who reported similar occurrences said, that doesn't seem to work. The connections tab just shows it open a batch of connections that just sit there "connecting" and counting up; then most of them disappear and are replaced; and so on. I can see a "dud connection checker" killing connections that aren't actually doing anything useful, but why would it then refuse to or be unable to establish replacement connections? Or are the dud connections and the failure to establish new ones both symptoms of an underlying problem? Yet where would that problem be -- the network stack? Any problem outside Limewire would have affected other applications. Web surfing and other activities worked normally. Only the enabling of a firewall that blocked non-surfing traffic, such as the sort often found in workplaces, could be a) external to limewire and b) so thoroughly cripple it while leaving other network apps alone, and nobody could have done that since I'm the one running the home network here. |
which version of java are you using? If it is not the latest 1.5.0_04, would mind trying that one? |
1.5.0_03 apparently. How does it get updated to 1.5.0_04? The downloads at sun's site don't distinguish any further than "1.5.0", so do I have to wait for 1.5.1 or something? |
|
Why is there a second, non-obvious Java download site at sun.com that's needed to stay up to date??? Anyway I'll try it... |
All times are GMT -7. The time now is 05:20 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.