How to resolve the "Diagnostics" errors?
I installed CLMv5.0.2 and getting the below errors in final "Diagnostics" report. Please suggest on how to remove this:
The system details are: OS: Windows Server2012, CLMv5.0.2, WASv8.5.5.5,IHSv8.5.0.2,Oraclev12C
Vendor: IBM Corporation
|
2 answers
Hi Pravin,
For the issue 1, please check if there's any detail error in jts.log For the issue 2, this is a known product defect https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=339546, which has been resolved in CLM 5.0.2 ifix002. You can download and apply the latest ifix to fix the issue. For the issue 3, this is a warning. You can ignore it, or set a time server for the CLM server Comments
Lily Wang
commented Apr 15 '15, 10:26 p.m.
After installing the fixpack I am running into issues and I don't see the deployed applications anymore which I use to see earlier. I also have PMR raised now. Below is the error:
The method getPrerequisiteServices() was called on the AbstractActivationManagerOwner for com.ibm.team.repository.service.internal.BaseServerDescriptionService when the service not activated. The method should only be called when the service is activated. If you see this error please report the problem to the Jazz Application Frameworks team, because there is a bug in the Jazz server.
com.ibm.team.repository.common.transport.internal.registry.ServiceNotActivatedException
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.getPrerequisiteServices(AbstractActivationManagerOwner.java:981)
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.withServiceDependencies(AbstractActivationManagerOwner.java:1339) com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.withServiceDependencies(OsgiServicesManager.java:775) com.ibm.team.repository.common.transport.internal.registry.ServiceConfiguration.validateProperties(ServiceConfiguration.java:430) com.ibm.team.repository.service.internal.ServerConfigurationRestService$2.processUpdate(ServerConfigurationRestService.java:338) com.ibm.team.repository.service.internal.ServerConfigurationRestService.processConfigUpdates(ServerConfigurationRestService.java:238) com.ibm.team.repository.service.internal.ServerConfigurationRestService.postConfigurationValidation(ServerConfigurationRestService.java:334) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) java.lang.reflect.Method.invoke(Method.java:611) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) com.sun.proxy.$Proxy392.postConfigurationValidation(Unknown Source) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) java.lang.reflect.Method.invoke(Method.java:611) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:567) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2453) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2244) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1761) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165) com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198) com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:191) com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:919) com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:287) com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049) com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:643) com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818) com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Pravin Patil
commented Apr 16 '15, 7:56 p.m.
After installing the fixpack I am running into issues and I don't see the deployed applications anymore which I use to see earlier. I also have PMR raised now. Below is the error: The method getPrerequisiteServices() was called on the AbstractActivationManagerOwner for com.ibm.team.repository.service.internal.BaseServerDescriptionService when the service not activated. The method should only be called when the service is activated. If you see this error please report the problem to the Jazz Application Frameworks team, because there is a bug in the Jazz server. |
Hi Pravin,
in addition to Lily's answer, I'd like to comment on you issue #3. If you installed all applications on the same server, this can be simply resolved by disabling the System Clock diagnostics. In this situation, disabling the diagnostic should be safe, since all applications will use the identical system time, i.e., there is no need to synchronise via NTP. However, if you deployed your applications on different hosts, you should configure NTP clock synchronisation. This can be done via the advanced properties The address of the NTP provider. If this value is blank, the system clock diagnostic cannot measure the system clock's accuracy.Once configured, the warning of the diagnostic should go away. |
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.