Unable to start Rhapsody-DM-Server for version 6.0.1 and 6.0.2 on win server 2012 R2.
I have downloaded "Rhapsody-DM-Servers-6.0.2" for trail purpose. I have installed it on windows server 2012 R2. when i try to start jts server, its shown me the below message.
INFO: Agent version "3.0.7.20160104"
Nov 23, 2016 1:29:58 PM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnector
WARNING: Failed to create RMI registry on port 1972: java.rmi.server.ExportException: Port already in use: 1972; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
Nov 23, 2016 1:29:58 PM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnector
INFO: IIOP will be listening on the next available system assigned port. Use com.ibm.java.diagnostics.healthcenter.agent.iiop.port to specify a port
Nov 23, 2016 1:29:58 PM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean startAgent
INFO: Health Center agent started on port 1973.
Starting server clm.
Server clm started.
It says Server started, but it does not start.
Any help would be appreciated!
Thanks in Advance.
One answer
https://jazz.net/forum/questions/229062/health-center-port-issue-on-startup-in-602
Comments
I tried to access https://localhost:9443/jts/web, but it fails to connect.
It can take several minutes for the application to get ready to display any pages. When you say fails to connect, what symptom is it? Have you checked whether the java process is running and/or showing any CPU usage? Have you used netstat command to verify whether port 9443 is open?
After I shutdown the server, the command netstat shows below message
It doesn't look right. Are you sure that after you shutdown the CLM server, the 9443 port is still open? If true, another process is occupying this port and you need to stop it first. Run command "netstat -aon | findstr LISTENING" to find out the PID of the process. Or use other methods mentioned in the below post.
http://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows
The issue got resolved by installing jts from CLM 6.0.2 bundle and RDM application from RDM server 6.0.2. I think there is some issue with the "Rhapsody-DM-Servers-6.0.2" setup