I have been working with RMI and having no problems starting the registry service. I have not explicitly changed anything. simply compiling, starting and then running the server.
Obviously something changed, but I do not know what to look for. I BELIEVE the stack trace looks something like this, actually its not the exact one because it opens the extra registry window and closes too quick to be able to capture it. I found this on the web, and for what i can see of mine, it looks similar.
can anyone point me in the direction of rmiregistry healing?
java.rmi.server.ExportException: Listen failed on port: 1099; nested exception i s: java.net.SocketException: Invalid argument: listen failed at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:245) at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178 ) 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:14 5) at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78) at sun.rmi.registry.RegistryImpl.main(RegistryImpl.java:317) Caused by: java.net.SocketException: Invalid argument: listen failed at java.net.PlainSocketImpl.socketListen(Native Method) at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:333) at java.net.ServerSocket.bind(ServerSocket.java:309) at java.net.ServerSocket.bind(ServerSocket.java:266) at java.net.ServerSocket.<init>(ServerSocket.java:182) at java.net.ServerSocket.<init>(ServerSocket.java:94) at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMI DirectSoc ketFactory.java:27) at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMI MasterSoc ketFactory.java:306) at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:61 5) at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231) ... 7 more
Please disregard. As simply as doing nothing to cause it, I did nothing to fix it. However, even after several reboots yesterday, it still did not work, but upon booting today, it works again.
Previous Topic
