It's all about the answers!

Ask a question

The server clm is stopping because the JVM is exiting.

Ram Gawande (1111) | asked Sep 26 '17, 7:44 a.m.

We are trying to start Collaborative lifecycle  Management(6.0.4) using Anisible playbook.Shutdown process gets successful but it is failing at the time of server.startup with below error.
Also when we try to start server.startup manually it works. but it fails though script
Script command in play book :-
name: Execute server start script
command: sh /home/jazz/6.0.4/Ansible_44443/server/server.startup


Ram Gawande commented Sep 26 '17, 7:46 a.m.

Error logs
[9/26/17 5:47:12:650 CDT] 0000001e id=            A CWWKF0012I: The server installed the following features: [ssl-1.0, appSecurity-2.0, json-1.0, jsp-2.2, restConnector-1.0, adminCenter-1.0, servlet-3.0, monitor-1.0, jaxrs-1.1, jndi-1.0, distributedMap-1.0].
[9/26/17 5:47:12:651 CDT] 0000001e id=            I CWWKF0008I: Feature update completed in 33.920 seconds.
[9/26/17 5:47:12:651 CDT] 0000001e id=       A CWWKF0011I: The server clm is ready to run a smarter planet.
[9/26/17 5:47:12:707 CDT] 00000013 id=  A CWWKE0085I: The server clm is stopping because the JVM is exiting.

One answer

permanent link
Donald Nong (14.5k514) | answered Oct 17 '17, 2:31 a.m.

If you search the error code CWWKE0085I, you should find the below two posts.

The explanation of the error code can be found here:

It seems that when the shell (you use "sh") exits, it also requests all the child processes (including Java) to quit. To avoid this, you need to find a way to not send a terminate signal (e.g. with "nohup") to keep Java running.

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.