Resolving an EAServer RMI Registry Port Conflict

If you experience problems when starting the SybAgent Server or deploying services to EAServer, the EAServer RMI default port number 1099 may be used by another application. Edit the EAServer SybAgent configuration file to resolve this port conflict.

To resolve an EAServer RMI Registry port conflict:

  1. Open the following file using a text or XML editor:

    Server Files

    FeatureSybase Developer Edition ServersUnwired Orchestrator Production Edition Server
    EAServer RMI Registry

    <installation directory>\WorkSpace\DevRuntimes\EAServer\SysMgmt\boot.xml

    <installation directory>\Orch-5_1\EAServer\SysMgmt\boot.xml

  2. Edit the port attribute in the RMI Registry element as in the following example:

    <mbean name="sybase.system.naming:Type=RMIRegistry"

    code="mx4j.tools.naming.NamingService">

    <attribute name=”Port”>1099</attribute>

  3. Search for instances of the default port number 1099 and replace all instances with the new and unique EAServer port number.

  4. Save and close the file.

  5. Close and relaunch Sybase WorkSpace.

Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com