It's all about the answers!

Ask a question

Active Services on JTS Server Admin shows stack trace


Peter Eichelsheim (61) | asked Feb 08 '11, 4:12 a.m.
Hello everyone,

After succesfully installing CCM and JTS version 3.0 we keep getting a stack trace in the Active Services screen in the status section. Does anyone know what's causing this and better how to get rid of this? (also it keeps showing : Loading Data.. on this page)

here the info:
com.ibm.team.repository.service.internal.ServerStatusRestService.getActiveServiceInfo

java.lang.Thread.getStackTraceImpl(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1147)
com.ibm.team.repository.service.internal.ServerStatusRestService.renderThreadStack(ServerStatusRestService.java:307)
com.ibm.team.repository.service.internal.ServerStatusRestService.getActiveServiceInfo(ServerStatusRestService.java:299)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:618)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
$Proxy66.getActiveServiceInfo(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:618)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:501)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:1832)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1688)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1598)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
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:75)
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:563)
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:420)
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)


Any help on this would be greatly appreciated.

Peter

3 answers



permanent link
Ard Wieringa (6) | answered Feb 14 '11, 6:31 a.m.
Here the same problem.

Running on windows7/64 with tomcat and derby. Nothing in the log files and there's no exception at the top of the stacktrace.

Anybody fixed this?

Ard

permanent link
Steven Tuttle (5079) | answered Apr 05 '12, 10:02 a.m.
I also have the same issue - has anyone figured this out? I have searched the forums and see similar people having issues, but no resolutions in the forums. If anyone has solved this, please post how it was solved. Thanks!

Steve

permanent link
Jared Russell (1.3k12019) | answered Apr 10 '12, 6:33 a.m.
There is no resolution as this isn't a problem. A stacktrace != an exception. The purpose of the stacktrace is to show what method is currently executing, so that you can see what is currently happening in the background service.

I also have the same issue - has anyone figured this out? I have searched the forums and see similar people having issues, but no resolutions in the forums. If anyone has solved this, please post how it was solved. Thanks!

Steve

Your answer


Register or to post 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.