CVS limewire won't connect

[mogunus]

My copy of CVS limewire, running on JRE 1.5.0_10 and built with javac 1.5.0_10, hangs on "starting connection" to the network. It also claims that my computer has a firewall running, which it doesn't. I'm running fedora core 6. There is no console output about this in Eclipse. Is all CVS currently broken like this or is this something that I'm doing wrong?

[Sam]

Have you ever been able to connect with LimeWire on your computer?

[mogunus]

Yes, limewire 4.12.6, rpm from the website running under my java 1.5.0_10 connects just fine and does not mistakenly detect a firewall.

[mogunus]

I just re-downloaded the cvs limewire code, and now it connects fine. Maybe I was doing something wrong? Oh, well.

[Sam]

Might have been a temporary glitch in the code. We do check in broken things every so often. :)

[xjh408]

I, too, am getting stuck in the "Starting Connection" mode. The major difference for me is that I've never successfully run LimeWire on this box (YellowDog 4.1 [2.6], PPC G4 Dual). I'm a long-time LimeWire user on the Mac, and have built (and successfully run) the same CVS version under Mac OSX.

This is on the 4.13 beta source, checked-out on 1/20/07, and refreshed (from Eclipse) daily.

If any logging is to be enabled, please let me know how to do so - I'm very new to Java programming (an old C programmer) and other than finding the log4j.properties file, I'm a bit lost.

FYI, the machine is behind a Sonicwall FW (as are my Macs), and nothing special is being done, for or against, LimeWire, to the best of my knowledge. Java[c] version 1.5.0.

[Sam]

If you run the packaged version once on that box, CVS will begin to connect okay.

[xjh408]

Sam:

Thanks for the tip, but while the just downloaded packaged version (LimeWireOther.zip) does indeed work, when I quit and run the beta, I have the same problem. However, one possible clue is that the packaged version won't terminate on its own - I start using the runLime.sh script, and upon doing a File->Close, the window closes, but the script doesn't finish. Only a 'kill -9' did the trick - I'm guessing that the 4.12 version didn't get the chance to update whatever bread-crumb it is that the 4.13 version would then use.

Any ideas?

Randy

[Sam]

Hmm -- odd that it isn't closing on it's own. A majority of the developers use Linux, and I would have thought we'd have caught that. The CVS version does close, though? Maybe it was just an issue in 4.13.0 that's since been fixed.

The reason running a production version atleast once is usually necessary is because we include some bootstrap hosts when we package the program up, and leave them out of CVS (otherwise those particular hosts tend to get hit a lot by folks who take the code and experiment with it). Unfortunately, the production version writes the hosts from memory to disk on shutdown, and if the program's not shutting down correctly...

There's a few ways around it. One is to figure out why it's not closing (I suspect it may be a 'Shutdown Option' in the options window needs to be changed), and the other is to take the 'gnutella.net' from your LimeWire preferences on OSX and copy it to the Linux box. On OSX this should be stored at ~/Preferences/LimeWire/gnutella.net, and Linux it would be ~/.limewire/gnutella.net.

Let us know how it goes. :)

[xjh408]

Found the problem. I had the Options->System Tray->Shutdown Behavior set to quit after any transfers had completed. Even though there were no transfers going on, this appeared to gum things up. I changed to quit immediately, and was able to get the 4.12 version to shutdown cleanly (and apparently update some files) and the 4.13 version now works correctly.

Thanks again for the leads.

Randy

[xjh408]

FYI, I wrote my last reply prior to seeing your response - your guess was dead on.

Randy

[Sam]

Awesome -- glad you got it working.

[donaldsash]

it keeps getting stuck on the content filtering. what do i need to do?

[ssimpala]

Make sure you are sharing a folder and that you are sharing some files in it.
Create a new one etc. dump some files there and try again!
This fixed it for me!