It's all about the answers!

Ask a question

RTC is not starting after upgrading from 5.0.2 to 6.0


Enrique Gaona (13462526) | asked Sep 23 '15, 3:14 p.m.
Hi,
I was wondering if anyone has encountered this issue before.   I just upgraded Linux RTC (JTS and CCM) from v5.0.2 to v6.0 and now the tool is dead in the water.   I see the java process, but the app server is not coming up.

All I see in the jts.log  2015-09-23 14:00:57,555 [Component Resolve Thread (Bundle 96)]  INFO nternal.OverridablePropertyFileServerConfiguration  - CRJAZ1363I Loading the configuration from "file:/opt/IBM/CLM60/server/conf/jts/teamserver.properties".   Has anyone seen this issue?   

System Info:
Red Hat Enterprise Linux Server release 6.3 (Santiago)
"DB2 v10.5.0.5"
Tomcat
RTC v6.0

JTS.log:
2015-09-23 14:00:36,073 [  Start Level Event Dispatcher]  INFO nternal.app.servlet.util.ServletDispatchingHandler  - CRJZS0315I Servlet Dispatching Enabled
2015-09-23 14:00:36,073 [  Start Level Event Dispatcher]  INFO nternal.app.servlet.util.ServletDispatchingHandler  - CRJZS0318I Servlet Loopback Disabled
2015-09-23 14:00:57,554 [Component Resolve Thread (Bundle 96)]  INFO nternal.OverridablePropertyFileServerConfiguration  -
 To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum.
 To find more information about a message, see the online product documentation.
2015-09-23 14:00:57,555 [Component Resolve Thread (Bundle 96)]  INFO nternal.OverridablePropertyFileServerConfiguration  - CRJAZ1363I Loading the configuration from "file:/opt/IBM/CLM60/server/conf/jts/teamserver.properties".


Comments
Kevin Ramer commented Sep 23 '15, 4:42 p.m.

Did you look at the Tomcat logs ( e.g. catalina.out ) ? 


Donald Nong commented Sep 24 '15, 12:54 a.m.

Have you verified that file /opt/IBM/CLM60/server/conf/jts/teamserver.properties is valid and readable?

One answer



permanent link
Enrique Gaona (13462526) | answered Sep 24 '15, 10:35 a.m.
Finally tracked down the culprit.   During the upgrade the 5.0.2 server.xml gets copied to the 6.0 directory, but not the server.startup script.  There was a missing element in the <Connector> that prevented the app server from starting. 

Kevin/Donald, thanks for the suggestions.

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.