Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

CLM 6: Errors when starting Starting the Jazz Team Server in a simple express setup environment

I have installed CLM 6 (JTS, RM, QM, CCM und JRS, Link Index Provider und Global Configuration) on a Windows Server 2012 R2 system.
I did the express setup
When I start the Jazz Team Server, I get ERRORs and WARNs.

13:19:13,524 [localhost-startStop-1] ERROR com.ibm.team.jis.lqe.load.LoadMonitor               - Unable to connect to IBM Health Center at <host> on port 1,972
13:19:13,524 [lqe.LoadMonitor-thread-0]  WARN com.ibm.team.jis.lqe.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"


Why do I get this error?
Ok, maybe I could try to install IBM Health Center, but for CLM 5 I did not recognize those messages. And I'm not interested in this Health Center.

Another effect: How can I see, if the tomcat has been stopped? The Window does not close and the java process is even after 5 minutes still there.

1

1 vote

Comments

I have noticed the same two issues.  
I just ignore the "IBM Health Center" warning message.
To shut down the server, I just kill it.   The "stop server" script doesn't work for me.

When I kill the server, I sometimes got more ERRORs (CRLQE0482E) reported talking about abnormal termination.



4 answers

Permanent link
I think that the IBM Health Center is standard with an IBM JRE but not turned on by default. Adding the JVM options is all you should need to do to turn on LQE performance monitoring. The overhead of turning on monitoring is < 1%. If you are running tomcat as a service, these JVM Options should be added in the same place you are setting up the "-DJAZZ_HOME" or "-Dlog4j.configuration" parameters.

1 vote


Permanent link
Now I have installed the RTC Eclipse 4.2 Client and the errors are gone.
Looks like the code used some debug stuff from a developers PC?!

Right now I have only two warnings left...
See this thread.

And Geoff, stopping is now working, too

0 votes

Comments

Unfortunately the errors are back after running the jts-setup


Permanent link
Hello,
This defect talks about being unable to stop the CLM 6.0 server:
Unable to shutdown Tomcat7 (349742)

Although it does not mention LQE errors, there are errors in several components. It may be that some underlying problem is causing multiple threads to continue unexpectedly.

Martha (Ruby) Andrews
Jazz Foundation L3 Development Team Lead


0 votes


Permanent link
Hello Dr. Hans,

Have you observed if the LQE was showing the node statistics about Status, Memory and CPU ?
LQE - Health Monitoring - Details
Select node

I saw a situation where first this issue was observed on LQE and then, checking the log files, the same message was presented: 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"
Environment using Websphere/Linux

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,499
× 5

Question asked: Jul 09 '15, 7:30 a.m.

Question was seen: 4,767 times

Last updated: Aug 21 '15, 1:08 p.m.

Confirmation Cancel Confirm