- This topic has 3 replies, 2 voices, and was last updated 18 years, 5 months ago by doug bloomfield.
-
AuthorPosts
-
doug bloomfieldParticipantHere is my system config:
Windows XP, Eclipse 3.2, MyEclipse 5.0, Tomcat 5.5.17, JDK 1.5.0_01I’ve just installed Eclipse 3.2, MyEclipse 5.0, and Tomcat 5.5.17. When I try to start tomcat, I get the following error output to the console after all the standard Tomcat startup stuff (if you want to see everything I can post it, but I thought for now this was sufficient):
INFO: Server startup in 3422 ms
Aug 10, 2006 9:39:35 AM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[8005]:
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:372)
at org.apache.catalina.startup.Catalina.await(Catalina.java:615)
at org.apache.catalina.startup.Catalina.start(Catalina.java:575)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)I was having a similar problem on Eclipse 3.1, MyEclipse 4.0. On that version, however, I could stop tomcat (even though I hadn’t really started it) and then restart it and it was fine. In this version the stop option is disabled and I can’t get around it. Can anyone tell me why Eclipse thinks the address is already in use? What have I missed here.
Thx
Scott AndersonParticipantHyrum,
Tomcat is indeed already running, or something else is on port 8080. What happened is that you’re likely running it as a Windows service so it starts at boot time. I’d suggest you check that and disable that service or it will always confound you a bit.
doug bloomfieldParticipantThanks for the quick response.
The original problem manifested itself on my co-workers computer. We are working on updating the MyEclipse installation so we can run the latest version of BIRT. The tomcat service was set to manual, but a reboot seemed to fix the issue.
I am, however, experiencing the same issue on my machine. I run Win2000(sp4), and have Eclipse 3.2, MyEclipse 5.0 and JDK 1.5. (The primary difference between my co-worker’s computer and mine is the operating system. He uses XP). I have been unable to get rid of the issue with a reboot. I have set the service to Disabled, tried a fresh reboot, opened nothing but Eclipse, and start Tomcat with the same result.
Please help!
doug bloomfieldParticipantI have solved the problem. The cause was the HP Toolbox I had installed when I installed my HP Printer a while back. If you have this toolbox installed, it will cause Tomcat problems, as it uses port 8005. That port is what Tomcat uses for shutdown.
I used a tool called ‘Active Port’ to find out who was using the port. It is distributed by the folks at http://www.tucows.com, and it is freeware. Once I discovered the culprit, I removed it from the registry, which has a list of Programs that run at startup. For Win2k, that list is found at HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Run. When I removed the Name for the HP Toolbox from that list and rebooted, everything worked fine.
Hope this helps someone else with any sort of JVM_Bind issues.
-
AuthorPosts