Consultor Eletrônico

Title : AdminServer Failing to Startup

This document applies to: Progress AdminServer
Version and Release Number: 9.0X

Summary:
This kbase will discuss one situation where the AdminServer failed to start up, and generated the following errors in the admserv.log file:
Failed RMI setup.. (8539)
AdminServer startup failed. See admserv.log for details. (8542)

Step by step details:

In this situation, there were also some other messages in the admserv.log file:
[*UnexpectedError*] * recorded as exception #<n> in file ads0.exp.

Looking in the ads0.exp file gave the following Java stack trace:

Exception at <date>: java.rmi.ConnectIOException
Message (throw): RegistryManager: PrimaryRegistryManager -
Could not bind name Chimera to object
com.progress.chimera.adminserver.AdminServer[RemoteStub [ref:
[endpoint:[XXX.XXX.XXX.XXX:1028](local),objID:[0]]]]
Message (excp): Error creating connection to: [<host1>:20931];
nested exception is:
java.net.SocketException: Connection refused
Stack Trace:
java.rmi.ConnectIOException: Error creating connection to: [<host1>:20931]; nested exception is:
java.net.SocketException: Connection refused
at sun.rmi.transport.tcp.TCPChannel.openSocket(TCPChannel.java:259)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:125)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:67)
at sun.rmi.registry.RegistryImpl_Stub.rebind(RegistryImpl_Stub.java:125)
at com.progress.common.rmiregistry.PrimaryRegistryManager$PrimaryBinder.call(PrimaryRegistryManager.java:210)
at com.progress.common.rmiregistry.TryIt.run(TryIt.java:186)

From the stack trace, the problem was that a socket connection was attempted, and the connection was refused by the host.

In this particular case, the host name set up on the machine was not the same as the hostname set up for the machine in the DNS. To resolve the issue, these were brought into line.

References To Written Documentation or Other KnowledgeBase Documents:

Progress Software Technical Support Note # 19309