JDK-8164901 : java/rmi/registry/multipleRegistries/MultipleRegistries.java failed because port conflicts
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2016-08-26
  • Updated: 2016-08-26
  • Resolved: 2016-08-26
Related Reports
Duplicate :  
Description
java/rmi/registry/multipleRegistries/MultipleRegistries.java failed in Mach5 with following exceptions:
java.rmi.server.ExportException: Port already in use: 63978; nested exception is: 
	java.net.BindException: Address already in use
	at sun.rmi.transport.tcp.TCPTransport.listen(java.rmi@9-internal/TCPTransport.java:335)
	at sun.rmi.transport.tcp.TCPTransport.exportObject(java.rmi@9-internal/TCPTransport.java:243)
	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(java.rmi@9-internal/TCPEndpoint.java:411)
	at sun.rmi.transport.LiveRef.exportObject(java.rmi@9-internal/LiveRef.java:147)
	at sun.rmi.server.UnicastServerRef.exportObject(java.rmi@9-internal/UnicastServerRef.java:209)
	at sun.rmi.registry.RegistryImpl.setup(java.rmi@9-internal/RegistryImpl.java:157)
	at sun.rmi.registry.RegistryImpl.<init>(java.rmi@9-internal/RegistryImpl.java:142)
	at java.rmi.registry.LocateRegistry.createRegistry(java.rmi@9-internal/LocateRegistry.java:203)
	at TestLibrary.createRegistryOnUnusedPort(TestLibrary.java:412)
	at MultipleRegistries.main(MultipleRegistries.java:68)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-internal/Native Method)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-internal/NativeMethodAccessorImpl.java:62)
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-internal/DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(java.base@9-internal/Method.java:535)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
	at java.lang.Thread.run(java.base@9-internal/Thread.java:843)
Caused by: java.net.BindException: Address already in use
	at java.net.PlainSocketImpl.socketBind(java.base@9-internal/Native Method)
	at java.net.AbstractPlainSocketImpl.bind(java.base@9-internal/AbstractPlainSocketImpl.java:437)
	at java.net.ServerSocket.bind(java.base@9-internal/ServerSocket.java:376)
	at java.net.ServerSocket.<init>(java.base@9-internal/ServerSocket.java:238)
	at java.net.ServerSocket.<init>(java.base@9-internal/ServerSocket.java:130)
	at sun.rmi.transport.tcp.TCPDirectSocketFactory.createServerSocket(java.rmi@9-internal/TCPDirectSocketFactory.java:45)
	at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(java.rmi@9-internal/TCPEndpoint.java:666)
	at sun.rmi.transport.tcp.TCPTransport.listen(java.rmi@9-internal/TCPTransport.java:324)
	... 15 more

Comments
Same issue has been introduced and covered by JDK-81019538
26-08-2016