OpenEdge 10.0B after install service pack 3 in windows2003.

Posted by mhtan88 on 21-Dec-2009 22:03

Spec:

OS: windows 2003 Enterprise Edition sp2

QuodCore 2.66Hz x2

16G RAM.

OpenEdge10.0B  03

hi all,

initially I have been using the same method to install in a new machine, there are no problem at all.

but after I migrated to a new machine. after install the 10.0B Openedge. Proadvs start with no problem.

after server pack 03 installed. the error shown as below:

Exception at Tue Dec 22 11:50:58 SGT 2009: java.rmi.server.ExportException

   Message (throw): RegistryManager: Could not start RMI Registry

   Message (excp):  Port already in use: 20931; nested exception is:

java.net.BindException: Address already in use: JVM_Bind

   Stack Trace:

java.rmi.server.ExportException: Port already in use: 20931; nested exception is:

java.net.BindException: Address already in use: JVM_Bind

at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)

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:145)

at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)

at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)

at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)

at com.progress.common.rmiregistry.PrimaryRegistryManager.startRMIRegistry(PrimaryRegistryManager.java:188)

at com.progress.common.rmiregistry.PrimaryRegistryManager.register(PrimaryRegistryManager.java:73)

at com.progress.chimera.adminserver.AdminServer.setupRMI(AdminServer.java:644)

at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:312)

at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:166)

at com.progress.chimera.adminserver.NTAdminServer.<init>(NTAdminServer.java:74)

at com.progress.chimera.adminserver.NTAdminServer.main(NTAdminServer.java:348)

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:324)

at com.progress.chimera.adminserver.AdminServerStarter.<init>(AdminServerStarter.java:74)

at com.progress.chimera.adminserver.AdminServerStarter.main(AdminServerStarter.java:88)

Caused by: java.net.BindException: Address already in use: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)

at java.net.ServerSocket.bind(ServerSocket.java:318)

at java.net.ServerSocket.<init>(ServerSocket.java:185)

at java.net.ServerSocket.<init>(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:615)

at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)

... 20 more

All Replies

Posted by egarcia on 22-Dec-2009 12:27

Hello,

This is an issue in 10.0B03.

There was a timing issue where the restart of the AdminServer was happening before the port was released.

This issue was fixed in 10.0B04.

I hope this helps.

Posted by mhtan88 on 22-Dec-2009 21:21

egarcia wrote:

Hello,

This is an issue in 10.0B03.

There was a timing issue where the restart of the AdminServer was happening before the port was released.

This issue was fixed in 10.0B04.

I hope this helps.

hi Egarcia,

Thank you for your information.  It did works. but, is there any way to patch or solved that particular problem( due to some reason that we don want to upgrade to 05)?

Thank you.

Regards,

TanMH

Posted by egarcia on 23-Dec-2009 08:42

Hello,

You are welcome.

If upgrading to 10.0B05 is not possible, you could just make sure that the port (20931) is available before the AdminServer is re-started. You could check that the AdminServer has shutdown by checking for the "shutdown complete" message in admserv.lg file or by checking the port using the netstat command.

Regards,

Edsel

This thread is closed