It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,033
×3,951

question asked: Apr 04 '13, 2:32 p.m.
question was seen: 4,297 times
last updated: Apr 24 '13, 9:26 p.m.

Related questions

RRC 4.0.2: Generate Document-Style Report stopped working after upgrade

0
Frank Ning (500●25●119●133) | asked Apr 04 '13, 2:32 p.m.
edited Apr 04 '13, 2:34 p.m.

Hello,

After I updated to CLM 4.0.2 from 4.0.1, the "Generate Document-Style Report" stopped working for RRC. After I clicked on "Finish", nothing happened on web UI. This is for CLM on Linux with DB2 and WAS.

I had another system on Windows 2008 and the "Generate Document-Style Report" still works after I upgraded CLM from 4.0.0 to 4.0.2. This issue happens to two seperate CLM servers on different Linux systems.

In the rm.log file, I see the following error:

2013-04-04 13:41:13,078 [             WebContainer : 13] ERROR ibm.rdm.fronting.server.rrs.publish.PublishService  - java.lang.IllegalStateException: Scheme 'unknown.https' not registered.
        at org.apache.http.conn.scheme.SchemeRegistry.getScheme(SchemeRegistry.java:80)
        at org.apache.http.impl.conn.DefaultHttpRoutePlanner.determineRoute(DefaultHttpRoutePlanner.java:107)
        at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:574)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:291)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
        at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
        at com.ibm.rational.dataservices.client.auth.oauth.OAuthCommunicator1a.executeImpl(OAuthCommunicator1a.java:413)
        at com.ibm.rational.dataservices.client.auth.oauth.OAuthCommunicator1a.execute(OAuthCommunicator1a.java:384)
        at com.ibm.rational.rpe.common.utils.URLDataProvider.doOAuth1a(URLDataProvider.java:346)
        at com.ibm.rational.rpe.common.utils.URLDataProvider.execute(URLDataProvider.java:442)
        at com.ibm.rational.rpe.common.utils.URLDataProvider.openDataStream(URLDataProvider.java:167)
        at com.ibm.rational.rpe.common.utils.URLDataProvider.openDataStream(URLDataProvider.java:183)
        at com.ibm.rational.rpe.common.template.api.impl.TemplateFileUtils.getAsFile(TemplateFileUtils.java:67)
        at com.ibm.rational.rpe.common.template.api.TemplateLoaderFactory.getLoader(TemplateLoaderFactory.java:40)
        at com.ibm.rational.rpe.engine.core.CoreUtils.loadTemplate(CoreUtils.java:60)
        at com.ibm.rational.rpe.api.docspec.DocumentSpecificationBuilder.loadTemplate(DocumentSpecificationBuilder.java:883)
        at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEDSXFiles.loadTemplate(PublishRPEDSXFiles.java:161)
        at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEDSXFiles.constructDocSpec(PublishRPEDSXFiles.java:214)
        at com.ibm.rdm.fronting.server.rrs.publish.internal.rpe.PublishRPEReports.getGenerateReportCommand(PublishRPEReports.java:356)
        at com.ibm.rdm.fronting.server.rrs.publish.internal.LegacyPublishService.doPost(LegacyPublishService.java:264)
        at com.ibm.rdm.fronting.server.rrs.publish.internal.PublishServiceInternal.doPostInternal(PublishServiceInternal.java:47)
        at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:689)
        at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:611)
        at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:138)
        at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:336)
        at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:214)
        at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:155)
        at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
        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:68)
        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:133)
        at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
        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.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:895)
        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:452)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
        at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
        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:1659)

Comments
Mike Jaworski commented Apr 04 '13, 2:45 p.m.
JAZZ DEVELOPER

 Hi Frank,


Has this environment undergone a server rename? There is a section of the stack trace which you posted mentioning an 'unknown.https' scheme, which seems like an improper mapping from a server rename. We recently had a case which seems similar to this come through IBM Support, so it's possible this could be the same issue.

You also mentioned other server(s) which you have tested this against ... can you confirm whether or not they have been renamed as well?

Thanks,
Mike Jaworski

Frank Ning commented Apr 04 '13, 7:04 p.m.

Hi Mike,

As I mentioned, this is for updating CLM including RRC from V4.0.1 to V4.0.2. It did not literally involve sever rename. I am not sure in the backend if Rational codes do server rename or not.

So from my (user) point of view, this is simply updating CLM from 4.0.1 to 4.0.2 (path 1 to path 2) on the same servers.

Please let me know if the fix Benjamin mentioned is indeed for this case as well since I already asked the PMR support engineer to get the fix which was mentioned by Benjamin.

Accepted answer

1
permanent link
Benjamin Silverman (4.1k●6●10) | answered Apr 04 '13, 2:42 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Frank,

This is a known issue.  The related work item is:

After server rename: Cannot create reports for reviews (55666)

Please contact IBM Rational Support if you require a fix for this issue.  Thanks,
Frank Ning selected this answer as the correct answer
Comments
Frank Ning commented Apr 04 '13, 2:49 p.m.

Thanks, Benjamin.

I opened a PMR to follow up to get the fix for this issue.

2 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Mike Jaworski (1.4k●6) | answered Apr 05 '13, 9:03 a.m.
JAZZ DEVELOPER
  Frank,

If your server has not undergone a server rename, I'm not sure if the fix that Ben mentioned would suffice or not. It's possible that this fix is not entirely related to servers which have been renamed though, so I could still be wrong ... Since you mentioned a recent CLM upgrade, I would attempt to reinitialize the publish service, since it may have been uninitialized during migration to the new version. See this article: http://www-01.ibm.com/support/docview.wss?uid=swg21600798

If this does not correct your problems, I would continue with the Support process to try to identify the root cause.

Thanks,
Mike
Comments
Frank Ning commented Apr 05 '13, 9:37 a.m.

It did not help.

I will let PMR support know your comment.

0
permanent link
Frank Ning (500●25●119●133) | answered Apr 24 '13, 9:26 p.m.

Just as reference, if you have service support from IBM and are having the same issue after RM is updated from 4.0.1 (or 4.0.0?) to 4.0.2, you may open a PMR to obtain the special hostfix for "APAR PM83850". This at least fixed the issue on my staging server (production server is going to be patched and tested).

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.