JTS not opening after installing rm and ccm
Hi,
As a part of evaluating the Jazz CLM applications. Initially I have installed rm with JTS on a standalone machine. which was working fine. Later on I found certain features like Requirements creation, workitem creation etc I was not able to complete.
Hence I installed the remaining two application rm and ccm on top of qm and JTS using IM installation went on well and after having restarted the JTS service everthing broke . Now I am unable to open the JTS admin page even.
Below are the log entries I have copied from JTS.log file.
(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:811)
Caused by:
org.apache.http.HttpException: While fetching the root services document from "https://abc.com:9443/qm/rootservices" a "404" HTTP status code was received
at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.validateRootServicesDocument(RootServicesUtil.java:477)
Let me know if this is a known issue or anyone got any suggestions.
As a part of evaluating the Jazz CLM applications. Initially I have installed rm with JTS on a standalone machine. which was working fine. Later on I found certain features like Requirements creation, workitem creation etc I was not able to complete.
Hence I installed the remaining two application rm and ccm on top of qm and JTS using IM installation went on well and after having restarted the JTS service everthing broke . Now I am unable to open the JTS admin page even.
Below are the log entries I have copied from JTS.log file.
(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:811)
Caused by:
org.apache.http.HttpException: While fetching the root services document from "https://abc.com:9443/qm/rootservices" a "404" HTTP status code was received
at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.validateRootServicesDocument(RootServicesUtil.java:477)
Let me know if this is a known issue or anyone got any suggestions.
One answer
Hi,
if you run the setup for JTS again, does it work then - can you reach JTS? Is RM? I am assuming you talk about CLM3.0.1.
I don't think this is a bug. My assumption is installing over - not sure how you did it I never tried - could have overwritten some configuration files. Server.xml, tomcat-users.xml and files in <installDir>/server/conf could be affected.
The message indicates that the JTS tries to get the root services document from QM and can't connect - maybe because it is not yet set up or because some properties are wrong.
It might be possible to fix the install if you have backups of the configuration files, or, maybe if you run setup and register QM and CCM. You can try that. It is probably easier to uninstall, or install in a new clean location and start all over, if you don't have production data that you need to recover.
PS: There is an article in the library https://jazz.net/library/ and information in the product help about backup that hint on files and file locations that are important.
if you run the setup for JTS again, does it work then - can you reach JTS? Is RM? I am assuming you talk about CLM3.0.1.
I don't think this is a bug. My assumption is installing over - not sure how you did it I never tried - could have overwritten some configuration files. Server.xml, tomcat-users.xml and files in <installDir>/server/conf could be affected.
The message indicates that the JTS tries to get the root services document from QM and can't connect - maybe because it is not yet set up or because some properties are wrong.
It might be possible to fix the install if you have backups of the configuration files, or, maybe if you run setup and register QM and CCM. You can try that. It is probably easier to uninstall, or install in a new clean location and start all over, if you don't have production data that you need to recover.
PS: There is an article in the library https://jazz.net/library/ and information in the product help about backup that hint on files and file locations that are important.