How do I resolve port conflicts between the RTM server and other applications that attempt to bind to the same port?
A. If nGenius RTM is installed on a system where no other applications use RMI port 1099, then port 1099 is used by RTM. If another application tries to bind to port 1099 while nGenius uses this port, the application fails to bind to port 1099 and the nGenius server continues working properly. However, if the nGenius server is not active when another application binds to port 1099, then the application continues to work successfully, but the nGenius Server is unable to start. To change the RMI port that RTM uses: • Manually edit RTMROOT/rtm/bin/serverprivate.properties and RTMROOT/rtm/html/client.properties files. • Set the RMIRegistryPort=11099 (or the next available TCP port.) The default is 1099.
Related Questions
- Are the client and server applications aware of the port number (and machine name, if applicable) where the Naming Service is running?
- How do I resolve port conflicts between the RTM server and other applications that attempt to bind to the same port?
- Why do I see a "Can start server : UNIX Bind : Permission denied" error message when I attempt to start msqld?
