RRC issues after upgrading from 4.0 to 4.0.1
Mike Ballard (68●1●6●10)
| asked Jan 11 '13, 2:04 p.m.
retagged Jan 11 '13, 2:31 p.m. by Laura W. Hinson (161●2●6)
We just finished upgrading from CLM 4.0 to CLM 4.0.1. All of the applications let me login, and seem to be functioning properly except for RRC. RRC allows me to login with no issues, but does not return any artifacts when attempting to view the artifacts. Instead the web console (eventually) gives the following error ( The application has been waiting for some time for the server to respond to a request.).
Prior to this error I saw an error that indicated that RRC could not determine if I had permissions to the project. However, I am not seeing this error any longer and don't know if it is related.
The rm.log file shows the following:
2013-01-11 18:40:55,489 [ http-bio-9443-exec-63] ERROR serPreferences.internal.UserPreferencesRestService - Server Error: Entry [c9d4429a06bd708f]
com.ibm.rdm.fronting.server.exception.ConflictException: com.ibm.rdm.fronting.server.exception.ConflictException
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:166)
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:147)
at com.ibm.rdm.fronting.server.core.jpi.internal.ServiceResponseHandler.statusCheck(ServiceResponseHandler.java:143)
at com.ibm.rdm.fronting.server.core.jpi.internal.ServiceResponseHandler.handleResponse(ServiceResponseHandler.java:53)
at com.ibm.rdm.fronting.server.core.jpi.internal.JTSStorageService.processHttpResponse(JTSStorageService.java:465)
at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.processResponse(CoreServiceRequest.java:64)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleCoreRequests(InternalCoreServices.java:658)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:317)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:246)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:232)
at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.executeServiceRequest(CoreServiceRequest.java:54)
at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:110)
at com.ibm.rdm.fronting.server.services.userPreferences.internal.UpdateUserPreferences.executeServiceRequest(UpdateUserPreferences.java:57)
at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:104)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalBaseServiceRequest.call(InternalBaseServiceRequest.java:83)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalBaseServiceRequest.call(InternalBaseServiceRequest.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:262)
at com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:55)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleExecutables(InternalCoreServices.java:579)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:319)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.executeRequestSequences(InternalCoreServices.java:939)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleRequestSequences(InternalCoreServices.java:798)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:314)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:246)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:232)
at com.ibm.rdm.fronting.server.core.jpi.internal.InternalBaseServiceRequest.executeRequestSequence(InternalBaseServiceRequest.java:114)
at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.executeRequestSequence(BaseServiceRequest.java:135)
at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:99)
at com.ibm.rdm.fronting.server.services.userPreferences.internal.UserPreferencesDomainService.doPostInternal(UserPreferencesDomainService.java:81)
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:722)
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:722)
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:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
at java.lang.Thread.run(Thread.java:738)
Request
PUT https://<host>:9443/jts/storage/com.ibm.rdm.userPreferences/cb5e319181a897794a15bf208ec13761 HTTP/1.1
If-Match: *
Content-Type: application/rdf+xml
Authorization: OAuth oauth_token_secret="xxx", oauth_nonce="xxx", oauth_token="xxx", oauth_consumer_key="xxx", oauth_signature_method="xxx", oauth_timestamp="xxx", oauth_version="1.0", oauth_signature="xxx"
--Start entity---
--End entity-----
Response:
HTTP/1.1 409
Server: Apache-Coyote/1.1
Cache-Control: private
Expires: Thu, 01 Jan 1970 00:00:00 UTC
Content-Type: text/html;charset=utf-8
Content-Length: 1313
Date: Fri, 11 Jan 2013 18:40:55 GMT
Content-Length: 1313
---Start entity---
<html><head><title>Apache Tomcat/7.0.25 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 409 - CRJZS0213E The request could not be completed due to a conflict with the current state of the resource.</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>CRJZS0213E The request could not be completed due to a conflict with the current state of the resource.</u></p><p><b>description</b> <u>The request could not be completed due to a conflict with the current state of the resource (CRJZS0213E The request could not be completed due to a conflict with the current state of the resource.).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.25</h3></body></html>
--End entity------
Any help would be very appreciated.
Thanks,
Mike
|
Accepted answer
|
Sorry for not posting the answer sooner.
Essentially, we and IBM PMR support could not figure out what the root cause of this was. I ended up restoring from our backup prior to the upgrade and performing the upgrade again. This was a while ago, so I don't remember all of the specifics, but eventually I was able to resolve the issues and get the application upgraded and working by starting over. Ralph Schoon selected this answer as the correct answer
|
4 other answers
@mballard: You may want to look at Project-specific suspicion preference isn't working correctly (68015) which may explain the error message. However, the error message may not be related to your problem. You may want to look at https://jazz.net/library/article/1212 and see if it may be related to your problem with artifacts.
Comments We are not using suspicion profiles. As for the article, I had already found that and rebuilt all the indexes using repotools. Any other thoughts? @mballard:That's as far as my knowledge of RRC goes. I think you should go ahead and file a defect or open a PMR at this point.
|
I have the "RRC could not determine if I had permissions to the project" error after upgrading from RRC 3.0.1.4 to 4.0.1. I have been working with IBM tech support for more than a week. Still not able to resolve it.
Comments @saranfepoc: We are going to file a PMR at this point. Hopefully one of us will have some success. |
How did everyone resolve this issue? Encountering it, too.
|
We are seeing similar message while trying to acknowledge it as "Reviewed". Were there any updates for this issue?
|
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.