Anyone seen this JVM error on a 6.2.1 Rcvr

Started getting intermittent deployment errors and this in the RCVR od.err log.

Thought it might be an IPv6 issue but no joy.

Sockets error: 0: JVM_Bind
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:251)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:184)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:78)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:186)
at com.interwoven.deploy.cdmain.IWCDMain.main(IWCDMain.java:1712)
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 com.interwoven.deploy.cdmain.IWCDBoot.run(IWCDBoot.java:255)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketException: Unrecognized Windows Sockets error: 0: 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.(ServerSocket.java:185)
at java.net.ServerSocket.(ServerSocket.java:97)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:622)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:237)
... 14 more

Find more posts tagged with

Comments

sheikh1

Have you checked that OD port 20014 is not already binded to another process or if any Daemon OD process already running/not killed?

Rick Poulin

Have you checked that OD port 20014 is not already binded to another process or if any Daemon OD process already running/not killed?

To add to this, JVM_Bind means that the JVM attempted to open a socket on a port that's already been used (as sheikh said), or a security policy or firewall prevents it from doing so. Given the 'intermittent' nature of the issue, I'd check for port scanners or overeager network protection, or anything that could get in the way of releasing ports.

'netstat -a -b -o' will help you identify the process(es) that are bound to the port, along with the PID and name of the owning executable. And since you're on Win2k8, [thread=38876]this may be related[/thread].