RTC server can not start
We deployed the RAM 7202 test fix 6, and in the RAM WAS console, now have the problem to start the RTC server. When we select this server, then click the "Restart" button, it always report the error "RTC server could not be started", in the SystemOut.log, it looks like this:
0000003e PmiRmArmWrapp I PMRM0003I: parent:ver=1,ip=10.100.10.42,time=1291701643936,pid=27746,reqid=2190,event=1 - current:ver=1,ip=10.100.10.45,time=1291704289397,pid=28732,reqid=16605,event=1 type=JDBC detail=java.sql.PreparedStatement.executeQuery() elapsed=0 0000003e PmiRmArmWrapp I PMRM0003I: parent:ver=1,ip=10.100.10.42,time=1291701643936,pid=27746,reqid=2190,event=1 - current:ver=1,ip=10.100.10.45,time=1291704289397,pid=28732,reqid=16606,event=1 type=JDBC detail=java.sql.Connection.commit() elapsed=0 0000003e WebApp E -: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: The server is not configured correctly and cannot process the request. Status kind=configurationNeeded at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:554) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1004) at com.ibm.ram.repository.web.RAMWSServletFilter.doFilter(RAMWSServletFilter.java:357) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:524) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3548) |
4 answers
Hi,
That's not an RTC error. The stack trace shown is a RAM error, so it is coming from the RAM server. If you are not in a cluster then by default RTC and RAM are on the same server, not on different servers. It is saying there is a configuration problem where it can't start the RAM web services app. The Web app should come up better and if you go there and login as a repository admin you should see what the configuration error is. Since you just applied testfix 6 my assumption is that it did not apply correctly. The status code of "configurationNeeded" typically is not a very bad error. It usually just means that you need to go to the configuration page and change some values, values that are no longer valid due to the testfix. If you are in a cluster and the RTC server isn't starting, this would also give you this error since RAM can't contact RTC. If you are in a cluster then RTC would be on a separate server. In that case you would need to supply the logs from that server. The little snapshot shown is not for RTC. Applying a testfix is very touchy. It is very important that the WAS servers that run RAM are NOT running when it is applied. This means that actual WAS server instance itself must not be running. If the servers are running there can be conflicts and the testfix will not apply correctly. However, the testfixes do not update RTC, so I don't know why it would be failing. Thanks, Rich |
Hi Rich,
Thank you for your explain. We are in a cluster , then the RTC and RAM are deployed in the different server. I also think the text fix is not the problem. Do you mean that I should search the detail log in the RTC server? Thanks. Hi, |
Hi,
Yes. If the problem is with RTC is not coming up on the server then you need to look at the log of the server that RTC is installed on to see why RTC is not coming up. -- Rich Kulp Rational Asset Manager developer |
OK. I got it, thanks a lot
Hi, |
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.