Are these errors anything to be concerned about? CLM 5.0.1 instance setup
Hi
I am setting up a new test instance of CLM 5.0.1 on windows 7 and derby (my normal test setup). After installation, I started the server from the commandline and all look well - except a warning that:
INFO: JSR 356 WebSocket (Java WebSocket 1.0) support is not available when runni
ng on Java 6. To suppress this message, run Tomcat on Java 7, remove the WebSock
et JARs from $CATALINA_HOME/lib or add the WebSocket JARs to the tomcat.util.sca
n.DefaultJarScanner.jarsToSkip property in $CATALINA_BASE/conf/catalina.properti
es. Note that the deprecated Tomcat 7 WebSocket API will be available.
comes up just after the admin.war deployment start. This is curious, as the shell says I am on Java v1.7 (ie Java 7) already.
No other errors noted.
Then I run setup - and there is an error on the Tomcat window after I start running jts/setup
INFO: Server startup in 123277 ms
2014-09-30 12:26:11,328 RQM [pool-25-thread-1] ERROR team.fulltext.service.inter
nal.FullTextServiceImpl - CRJAZ2671E The "com.ibm.rqm.execution.service.interna
l.query.ExecutionResultIndexingParticipant" service failed to activate because a
service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", i
s not registered.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671
E The "com.ibm.rqm.execution.service.internal.query.ExecutionResultIndexingParti
cipant" service failed to activate because a service that it depends on, "com.ib
m.rqm.common.service.IPagedSearchService", is not registered.
Setup finishes ok on the webUI and I can create new users and add in token licenses.
Are these errors anything to be worried about?
thanks
anthony
I am setting up a new test instance of CLM 5.0.1 on windows 7 and derby (my normal test setup). After installation, I started the server from the commandline and all look well - except a warning that:
INFO: JSR 356 WebSocket (Java WebSocket 1.0) support is not available when runni
ng on Java 6. To suppress this message, run Tomcat on Java 7, remove the WebSock
et JARs from $CATALINA_HOME/lib or add the WebSocket JARs to the tomcat.util.sca
n.DefaultJarScanner.jarsToSkip property in $CATALINA_BASE/conf/catalina.properti
es. Note that the deprecated Tomcat 7 WebSocket API will be available.
comes up just after the admin.war deployment start. This is curious, as the shell says I am on Java v1.7 (ie Java 7) already.
No other errors noted.
Then I run setup - and there is an error on the Tomcat window after I start running jts/setup
INFO: Server startup in 123277 ms
2014-09-30 12:26:11,328 RQM [pool-25-thread-1] ERROR team.fulltext.service.inter
nal.FullTextServiceImpl - CRJAZ2671E The "com.ibm.rqm.execution.service.interna
l.query.ExecutionResultIndexingParticipant" service failed to activate because a
service that it depends on, "com.ibm.rqm.common.service.IPagedSearchService", i
s not registered.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ2671
E The "com.ibm.rqm.execution.service.internal.query.ExecutionResultIndexingParti
cipant" service failed to activate because a service that it depends on, "com.ib
m.rqm.common.service.IPagedSearchService", is not registered.
Setup finishes ok on the webUI and I can create new users and add in token licenses.
Are these errors anything to be worried about?
thanks
anthony
2 answers
Hi Anthony,
The error after the startup appears to be:
https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=123705
With regards to the JSR 356 WebSocket error. not sure we've seen this before. What does java -version return?
It is merely INFO, so as we've not seen that before I wouldn't be worried.
Cheers,
Paul
The error after the startup appears to be:
https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=123705
With regards to the JSR 356 WebSocket error. not sure we've seen this before. What does java -version return?
It is merely INFO, so as we've not seen that before I wouldn't be worried.
Cheers,
Paul