RQM Error fetching server status information.ID CRJAZ1505E
The JTS(version 4.0.1) is installed on a ubuntu machine.
The database is DB2 (version 10.1.0).
We can login the jts by web(https://9.115.249.158:9443/jts/admin).
However, if we click any items on the server(status summary,diagnostics,license key management etc...), the server will complain "Error fetching server status information.ID CRJAZ1505E".
Check the jts.log on the machine, we'll find the following info:
=====jts.log===
2013-06-26 15:09:33,342 [ http-bio-9443-exec-24] ERROR net.jazz.ajax.service.internal.http.ThemingHandler - ERROR : GET https://9.115.249.158:9443/jts/_theming/allThemeJS HTTP/1.1
org.apache.http.HttpException: Problem initializing theme namespace
at net.jazz.ajax.service.internal.http.ThemingHandler.getHttpException(ThemingHandler.java:1510)
at net.jazz.ajax.service.internal.http.ThemingHandler.initMetadata(ThemingHandler.java:1502)
at net.jazz.ajax.service.internal.http.ThemingHandler.init(ThemingHandler.java:349)
at net.jazz.ajax.service.internal.http.ThemingHandler.handle(ThemingHandler.java:276)
at com.ibm.team.server.httpcore.bridge.AbstractHandlerWrapperServlet.doWrappedService(AbstractHandlerWrapperServlet.java:139)
at net.jazz.ajax.service.internal.AjaxServices$1.doWrappedService(AjaxServices.java:151)
at com.ibm.team.server.httpcore.bridge.AbstractHandlerWrapperServlet.service(AbstractHandlerWrapperServlet.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:738)
Caused by: java.lang.NullPointerException
at net.jazz.ajax.service.internal.http.ThemingHandler.sendLocalRequest(ThemingHandler.java:1663)
at net.jazz.ajax.service.internal.http.ThemingHandler.sendJfsRequest(ThemingHandler.java:1653)
at net.jazz.ajax.service.internal.http.ThemingHandler.sendBasicJFSGet(ThemingHandler.java:605)
at net.jazz.ajax.service.internal.http.ThemingHandler.createRootNamespace(ThemingHandler.java:1521)
at net.jazz.ajax.service.internal.http.ThemingHandler.initMetadata(ThemingHandler.java:1481)
... 33 more
========jts.log=========
The DB2 is started and listenning the port of 50000:
[root@guangzhou version]# netstat -npl|grep -i 50000
tcp 0 0 0.0.0.0:50000 0.0.0.0:* LISTEN 5854/db2sysc 0
Is there any clue to fix the problem?
Thanks,
Sean
4 answers
I would probably try to connect to JTS db using the username that you used during jts setup to see if the user id is locked or password expired etc if you have not used the instance owner itself. Like "db2 connect to JTS user <mydb2user> using <password>
Your database is not local right ? and you are using Tomcat ?
Your database is not local right ? and you are using Tomcat ?
Hu Jiale, Is CLM running as a tomcat service?
I see similar problems observed with CLM started as tomcat service.
Did you try re-starting the service? i.e., stop - clear any stray "java.exe" processes - restart the service..
Check if the ubuntu user starting the service has "root" priveleges?
How about other context roots "qm/admin" OR "ccm/admin"? If they have similar errors also; re-check after a restart?
Might need to look at the logs to see if there is anything specific to be done..
Best Regards, Sunil
Although absolutely unsure but to me it looks like there are some issues with database connectivity. Check if the applications are actually connected to the databases. You can run "db2 list active databases" on the db2 server to see if there are any active connections exists on the application databases, specially to the JTS db once you login to jts/admin.
If not and assuming this is a new DB2 instance, try running db2set DB2COMM=tcpip on the db2 server, restart the application server and see if that works.
If not and assuming this is a new DB2 instance, try running db2set DB2COMM=tcpip on the db2 server, restart the application server and see if that works.
Hi Indradri,
"db2 list active databases" shows there's no connections to the databases.
####log####
[db2inst1@guangzhou ~]$ db2 list active databases
SQL1611W No data was returned by Database System Monitor.
However, I can connect to jts manually by the command of"db2 connect to jts"
=====Log=====
[db2inst1@guangzhou ~]$ db2 connect to jts
Database Connection Information
Database server = DB2/LINUXX8664 10.1.0
SQL authorization ID = DB2INST1
Local database alias = JTS
db2inst1@guangzhou ~]$ db2 list active databases
Active Databases
Database name = JTS
Applications connected currently = 1
Database path = /home/db2inst1/db2inst1/NODE0000/SQL00001/MEMBER0000/
I tried running db2set DB2COMM=tcpip and then restart the app. server and got the same results.
Any more ideas?
Thanks,
Sean
Comments
Hi Indradri,
Seems that the password expired for the user ID.
After reset the password the connection to DB2 is OK now.
The password for the userID will be changed in two days though PASS_MAX_DAYS is set to 90. We're checking why the password will be expired no more than two days.
Thanks,
Sean