After upgrade of RRC from 4.0.1 to 4.0.6 traceability reports get error
We upgraded our CLM environment (jts,ccm,qm,rm) from 4.0.1 to 4.0.6. The upgrade went fine with no apparent problems. We also at the same time upgraded WebSphere from 8.0.0. to 8.5. All seems to be working ok except when trying to create RM traceabilty reports. When we request to create one we just just get a message "the process has started" and it just hange there and nothing gets produced. In the rm.log file we see this error:
We need to get the traceability reports working - any suggestions??
2014-08-06 08:18:39,126 [ WebContainer : 9] ERROR ibm.rdm.fronting.server.rrs.publish.PublishService - com.ibm.rational.rpe.common.template.api.DataReferenceException: Invalid data reference <moduleDispayName> in condition. Query handle is $7 and absolute query path is <dataSource/artifact/moduleContext/contextBinding/moduleDispayName>.
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForDataExpression(TemplateLoaderImpl.java:466)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForScript(TemplateLoaderImpl.java:486)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForExpression(TemplateLoaderImpl.java:521)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:583)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:610)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:610)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:610)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:610)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinksForElement(TemplateLoaderImpl.java:610)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.buildLinks(TemplateLoaderImpl.java:266)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl$LinkBuilder.access$1(TemplateLoaderImpl.java:197)
at com.ibm.rational.rpe.common.template.api.impl.TemplateLoaderImpl.loadTemplate(TemplateLoaderImpl.java:1135)
at com.ibm.rational.rpe.engine.core.CoreUtils.loadTemplateImpl(CoreUtils.java:100)
at com.ibm.rational.rpe.engine.core.CoreUtils.loadTemplate(CoreUtils.java:79)
at com.ibm.rational.rpe.api.docspec.DocumentSpecificationBuilder.loadTemplate(DocumentSpecificationBuilder.java:837)
at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEDSXFiles.loadTemplate(PublishRPEDSXFiles.java:165)
at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEDSXFiles.constructDocSpec(PublishRPEDSXFiles.java:218)
at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEReports.getGenerateReportCommand(PublishRPEReports.java:358)
at com.ibm.rdm.fronting.server.rrs.publish.internal.LegacyPublishService.doPost(LegacyPublishService.java:294)
at com.ibm.rdm.fronting.server.rrs.publish.internal.PublishServiceInternal.doPostInternal(PublishServiceInternal.java:50)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:831)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:710)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:147)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:433)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:239)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:159)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:285)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
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:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3703)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)
|
2 answers
|
We opened a MR with IBM and they had me run a command to re-initialize publishing and that fixwed the problem,
|
Excellent!
I proof this and work fine. I have suite jazz 4.0.6, 1.- proof erase folder: "temporary folder where the files are usually stored for example, [SERVER_INSTALL]/server/tomcat/temp/rrc_reports/rrdg" 2.- And reinitialize the service "Publish Service". |
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.
Comments
I think I have heard about the same problem on large views or modules. Just to confirm, have you tested using the same Traceability report but with a module smaller? Try with a module with fer module artifacts.
We have tried to create the report on a single artifact and still the same problem. One thing we did do was make a series of changes to some of the RM configurations where an existing component was renamed, some properties were created and removed and a new link type was defined. This was after the upgrade and unfortunately we did not try a traceability report after the upgrade to 4.0.6 but before making the RM configuration changes. Could it be related to those configuration changes? Are there other things I can look at to determine the specifics regard the $7 parameter?
I think those changes make me think that they could be related. What changes you are talking about? can you try to back out those changes and try to recreate (as of just after upgrade to 4.0.6)?