Cannot start Jazz Server-error with no specific handler
My locally installed Jazz Team Server didn't shutdown correctly, due to a machine crash. After rebooting and starting JTS for CLM v3 beta M12. I cannot log into the Requirements section RRC.
Are there any ways of getting my CLM requirements work back without a full reinstall?
I want to keep my data.
Error message:
![]()
![]()
Are there any ways of getting my CLM requirements work back without a full reinstall?
I want to keep my data.
An error has occurred while processing a server request. The server returned error code 500
ID CRRRW7553E A message that was received from the server indicates an error with no specific handler.
Unable to load /rm/proxy?uri=https%3A%2F%2Frrc3%3A9444%2Fjts%2Fwhoami&dojo.preventCache=1298293293443 status:500
Error("Unable to load /rm/proxy?uri=https%3A%2F%2Frrc3%3A9444%2Fjts%2Fwhoami&dojo.preventCache=1298293293443 status:500")@:0 ([object Object])@https://rrc3:9444/rm/web/_js/?include=A~&etag=DNTce4nhA_en_US:17 ()@https://rrc3:9444/rm/web/_js/?include=A~&etag=DNTce4nhA_en_US:17 (3)@https://rrc3:9444/rm/web/_js/?include=A~&etag=DNTce4nhA_en_US:17
URL: /rm/proxy?uri=https%3A%2F%2Frrc3%3A9444%2Fjts%2Fwhoami
Unexpected exception : HTTP/1.1 503 Service Unavailable Server:Apache-Coyote/1.1 Content-Type:text/html;charset=utf-8 Content-Length:1324 Date:Mon, 21 Feb 2011 13:01:33 GMT Connection:close net.jazz.ajax.service.internal.http.ProxyHandler.processOAuthAuthorizationRequiredResponse(ProxyHandler.java:848) net.jazz.ajax.service.internal.http.ProxyHandler.forwardToUri(ProxyHandler.java:559) net.jazz.ajax.service.internal.http.ProxyHandler.handle(ProxyHandler.java:451) com.ibm.team.server.httpcore.bridge.AbstractHandlerWrapperServlet.doWrappedService(AbstractHandlerWrapperServlet.java:136) net.jazz.ajax.service.internal.EndpointRegistrar$1.doWrappedService(EndpointRegistrar.java:83) com.ibm.team.server.httpcore.bridge.AbstractHandlerWrapperServlet.service(AbstractHandlerWrapperServlet.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:62) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) java.lang.Thread.run(Thread.java:811)
Accepted answer
4 other answers
I thought I'd have a go at reinstalling CLM v3 beta M12. Everything worked again. But closing down the server just hung and didn't close properly. Now when restarting the Jazz Server I get the similar errors to before, see screenshot of error msg
http://dl.dropbox.com/u/2677078/jts_error.png
http://dl.dropbox.com/u/2677078/jts_error.png
http://dl.dropbox.com/u/2677078/jts_error.png
I thought I'd have a go at reinstalling CLM v3 beta M12. Everything worked again. But closing down the server just hung and didn't close properly.
First point - the server does take a while to shut down as it cleans up all the apps. Wait a few minutes after you start the shutdown to give it time to clean up.
I have seen those warnings before - they do not seem to change the behaviour so may be ok to ignore.
regards
anthony
I'm seeing the same exact issue. I've tried giving the server a few hours to shut down but the service never ends properly. The next time I try to start up the server I see the same 500 http error and can't get to the server.
I faced this issue after RM application had a sudden crash. Restarting the server didn't help.
Steps that worked out for me eventually:
Stop JTS
Delete all files under:
C:\Progra~1\IBM\JazzTeamServer\server\tomcat\work\Catalina\localhost\rm\proxyTemp
C:\Progra~1\IBM\JazzTeamServer\server\tomcat\work\Catalina\localhost\jts\proxyTemp
C:\Progra~1\IBM\JazzTeamServer\server\tomcat\temp
Start JTS and wait for 15 minutes before logging into any JTS application.
`