nainil
asked on
Need some help resolving Tomcat Java Error (Unrecognized Windows Sockets error: 0: JVM_Bind)
I am trying to run a web application on Tomcat 5. Getting a java.net.SocketException. Google search seemed to indicate that this may be due to another application using a port that Tomcat server is trying to use. I changed the port to 50000 range, and still get the same error:
Mon Jul 19 16:53:00 CDT 2010: Starting to listen to port 50002
Mon Jul 19 16:53:00 CDT 2010
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.s ocketBind( Native Method)
at java.net.PlainSocketImpl.b ind(PlainS ocketImpl. java:359)
at java.net.ServerSocket.bind (ServerSoc ket.java:3 19)
at java.net.ServerSocket.<ini t>(ServerS ocket.java :185)
at java.net.ServerSocket.<ini t>(ServerS ocket.java :97)
at catalog.Engine.PortListene r(Engine.j ava:324)
at catalog.Engine.execute(Eng ine.java:1 21)
at org.quartz.core.JobRunShel l.run(JobR unShell.ja va:195)
at org.quartz.simpl.SimpleThr eadPool$Wo rkerThread .run(Simpl eThreadPoo l.java:520 )
Mon Jul 19 16:53:00 CDT 2010: Starting to listen to port 50002
Mon Jul 19 16:53:00 CDT 2010
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.s
at java.net.PlainSocketImpl.b
at java.net.ServerSocket.bind
at java.net.ServerSocket.<ini
at java.net.ServerSocket.<ini
at catalog.Engine.PortListene
at catalog.Engine.execute(Eng
at org.quartz.core.JobRunShel
at org.quartz.simpl.SimpleThr
Looks like it could be Quartz-related. Can you reboot the box and try again?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@chej: I tried that. did not help.
@objects: Correct, the catalog.engine is opening the port. I changed the limits from 3000-50000 (randomly), but the same error.
This works on another server we have deployed (same catalog.engine). I am unable to point out where the server config is going wrong.
@objects: Correct, the catalog.engine is opening the port. I changed the limits from 3000-50000 (randomly), but the same error.
This works on another server we have deployed (same catalog.engine). I am unable to point out where the server config is going wrong.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@objects: I did verify there is only one engine started.
whats netstat tell you?
any firewalls etc that could be blocking opening ports?
any firewalls etc that could be blocking opening ports?
ASKER
nothing as yet.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It did not help... Well, any ways, thank you for your help! will go for a clean install and see what is happening.