It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,883
×10,958
×7,479
×6,033
×5,944
×4,320

question asked: Oct 06 '16, 8:01 a.m.
question was seen: 4,648 times
last updated: Dec 14 '16, 10:42 a.m.

Related questions

Health center port issue on startup in 602

0
Norman Dignard (356●6●96●177) | asked Oct 06 '16, 8:01 a.m.
We upgraded from 502 to 602 ifix3 single install, using liberty and oracle backend on RHEL 6.4. Done as root.
On startup , returned to the console screen we see:

[root@jazz server]# ./server.startup

May 12, 2016 8:44:00 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean <init>INFO: Agent version "3.0.7.20160104"May 12, 2016 8:44:01 AM 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 portMay 12, 2016 8:44:01 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean  startAgentINFO: Health Center agent started on port 1972.Starting server clm.Server clm started with process ID 56229.
**************
Looking at the console.log it shows:

In console.log get

May 12, 2016 8:44:01 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean <init>

INFO: Agent version "3.0.7.20160104"May 12, 2016 8:44:01 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnectorWARNING: 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
May 12, 2016 8:44:01 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean createJMXConnectorINFO: IIOP will be listening on the next available system assigned port. Use com.ibm.java.diagnostics.healthcenter.agent.iiop.port to specify a portMay 12, 2016 8:44:01 AM com.ibm.java.diagnostics.healthcenter.agent.mbean.HCLaunchMBean startAgentINFO: Health Center agent started on port 1973.

*********************

No issue there until you look at the lqe and ldx logs:

2016-09-21 12:09:55,900 [    Default Executor-thread-56] ERROR com.ibm.
team.jis.lqe.health.load.LoadMonitor        - Unable to connect to IBM
Health Center at jazz.navcanada.ca on port 1,972
2016-09-21 12:10:05,928 [      lqe.LoadMonitor-thread-0]  WARN com.ibm.
team.jis.lqe.health.load.LoadMonitor        - Unable to gather all
performance metrics. Please install and enable IBM Health Center in the
JVM. If you are running Tomcat, you will need to add the following JVM
options to the startup script. "-agentlib:healthcenter -Dcom.ibm.java.
diagnostics.healthcenter.agent.port=1972"

*************************************************

Has anyone else had this issue?  Where is the port defined as I can't find in in any properties file?








2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered Oct 07 '16, 1:16 a.m.
The configuration is in the server.startup script.
set HEALTHCENTER_OPTS=-agentlib:healthcenter -Dcom.ibm.java.diagnostics.healthcenter.agent.port=1972
The funny thing is, it seems that I always have such problem on Windows, but never on Linux.
Comments
Norman Dignard commented Oct 19 '16, 8:11 a.m.

Thanks for point out the file defining the port. 

Have you experienced the agent port issue in v6?  I've raised a PMR to clarify what the issue is.  I have 3 different instances of JAZZ setup and all report the same. All apps installed and started as root using Liberty.  On initial start-up returned to the terminal it states is started on 1972. A few seconds later in the console.log it reports 1972 in use and restarted on 1973.  Once lde and ldx startup they complain can't find the agent on 1972.

In a brief discussion with a IBM rep on this, he stated that this is used with the Health Monitoring system , a separate app install. We have not used or set this up so what gives?

Donald Nong commented Oct 19 '16, 8:55 p.m.

Indeed it is for the Health Center tool, which is part of the IBM Java toolkit, not specific to CLM. You can find more details here:
https://www.ibm.com/developerworks/java/jdk/tools/
http://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/topics/enablingagent.html

LQE and LDX can report the "health" or performance level of each node, so chances are they are actually using this port.

0
permanent link
Dmitry Lapygin (11●1●2) | answered Dec 14 '16, 10:42 a.m.
 I have the same problem with 6.0.2 and only RM installed on server. JTS, RS, DCC and LQE on other server have this problem too. But not always.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.