Resolving an EAServer RMI Port Conflict

The RMI registry listener port is the location where the RMI registry is started. To resolve port conflicts for Service Containers, change any duplicate port numbers for the RMI listener in the EAServer Manager.

Problem: Port conflicts typically manifest as SRVLIB message: Net-Library routine net_listener (host:port) failed in srv_start_listeners or Network error: status = 23 - Net-Lib protocol driver call to register a listener failed.

Solution: Change duplicate port numbers that exist. Duplicate port numbers typically occur when multiple default RMI ports are used.

Open the listener properties. In the EAServer Management Console, click Resources > Listeners.
Search for instances of duplicate port numbers by double-clicking the data source and reviewing the contents of the General tab. For example, frequently the default port number might be inadvertently used. Therefore, check for 7700 on this tab and change the default port number to a new, unused RMI port number.
Restart the EAServer

For detailed information, see the EAServer documentation located at the main level of the Sybase WorkSpace online bookshelf. If this server documentation is not installed, the documentation is available on the Sybase Product Manuals Web site at http://sybooks.sybase.com. . Specifically, for a list of default ports used, see Chapter 2, "Installing EAServer" in the EAServer Installation Guide. For information on how to enable RMI-IIOP tracing, see Chapter 1 of the Troubleshooting Guide, which describes how to enable RMI-IIOP tracing. You can also refer to the System Administration Guide, which describes how the RMI ports are used.