CLM 5.0 + RHEL 6.5: error registering a second CCM application
Hi,
I'm trying to setup a second ccm application, but when registering the second application through jts/setup I keep getting the following error:
4 answers
Are you using Websphere? There is a virtual host configuration option in Websphere, see:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_configuring_virtual_hosts.html
(this is from the 4.0.1 Information center, but the steps are pretty much the same)
Make sure your virtual host is configured properly. Otherwise, I would recommend checking the WAS logs for that application and seeing if there are any errors there.
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_configuring_virtual_hosts.html
(this is from the 4.0.1 Information center, but the steps are pretty much the same)
Make sure your virtual host is configured properly. Otherwise, I would recommend checking the WAS logs for that application and seeing if there are any errors there.
This is the error I get in the logs:
Jul 14, 2014 4:27:58 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [equinoxbridgeservlet] in context with path [/demo] threw exception
Throwable occurred: java.lang.IllegalStateException: Cannot call sendError() after the response has been committed
at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:450)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:78)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.initialize(BridgeFilter.java:319)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:196)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:610)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:312)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:761)
I am quite sure your second CCM application is not deployed correctly and it has little to do with JTS. Simply try the URL https://myurl:9443/demo/scr or https://myurl:9443/demo/ in your browser. If you get the same HTTP 404 error, you need to check the deployment of the second CCM application.
I did a quick and dirty test in both my 4.0.5 and 5.0 environments and had no difficulties with bringing up the second CCM application. Here are what I did.
1. Copy server/conf/ccm to server/conf/demo
2. Modify server/conf/demo/teamserver.properties by changing the paths to "demo".
3. Copy server/tomcat/webapps/ccm.war to server/tomcat/webapps/demo.war.
4. Start Tomcat.
That's it really. I can see the login page if I access https://<server>:9443/demo, or get an XML output if I access https://<server>:9443/demo/scr. I have not checked carefully whether I need to change anything else but that should get you started anyway.
Note: I did not register the second CCM "demo" in JTS since I don't want to keep it in my environment.
When checking catalina.out, make sure that there are no errors after the line saying deploying demo.war.
I did a quick and dirty test in both my 4.0.5 and 5.0 environments and had no difficulties with bringing up the second CCM application. Here are what I did.
1. Copy server/conf/ccm to server/conf/demo
2. Modify server/conf/demo/teamserver.properties by changing the paths to "demo".
3. Copy server/tomcat/webapps/ccm.war to server/tomcat/webapps/demo.war.
4. Start Tomcat.
That's it really. I can see the login page if I access https://<server>:9443/demo, or get an XML output if I access https://<server>:9443/demo/scr. I have not checked carefully whether I need to change anything else but that should get you started anyway.
Note: I did not register the second CCM "demo" in JTS since I don't want to keep it in my environment.
When checking catalina.out, make sure that there are no errors after the line saying deploying demo.war.
Comments
Hey Donald, the demo application does not have a .log file, not even a .metadata folder. The ccm application does have one...
Everything else in that directory looks exactly the same though...
Comments