Why can I not edit artifacts in RRC after upgrade to V403?
|
|
Accepted answer
I do not know what the real issue was, that my migration of the RRC links failed.
What I did to solve the problem:
Maybe IBM support can reproduce. Ralph Schoon selected this answer as the correct answer
|
One other answer
|
2013-06-25 22:26:30,037 [ RM-Task-Executor-1] INFO ver.services.locks.internal.LockServiceInitializer - Initializing lock service... 2013-06-25 22:26:30,115 [ RM-Task-Executor-1] INFO erver.services.locks.internal.LockResourceUpgrader - Lock resources storage area needs to be initialized or lock resources need to be upgraded. 2013-06-25 22:26:30,115 [ RM-Task-Executor-1] INFO ver.services.locks.internal.LockServiceInitializer - Upgrading lock graphs... 2013-06-25 22:26:30,146 [ RM-Task-Executor-1] INFO erver.services.locks.internal.LockResourceUpgrader - Lock resource version identifier is: null 2013-06-25 22:26:30,771 [ RM-Task-Executor-1] INFO erver.services.locks.internal.LockResourceUpgrader - Upgrading lock resources. 1 locks found. 2013-06-25 22:26:30,771 [ WebContainer : 1] ERROR serPreferences.internal.UserPreferencesRestService - Server Error: Entry [8572fae429f3516d] com.ibm.rdm.fronting.server.exception.BadRequestException: Propagated exception; original message [Propagated exception; original message [com.ibm.rdm.fronting.server.exception.BadRequestException]] at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:178) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:649) at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:653) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.checkError(InternalServiceExchange.java:53) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.getResponse(InternalServiceExchange.java:37) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalBaseServiceRequest.executeRequestSequence(InternalBaseServiceRequest.java:116) 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:770) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:687) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:142) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:409) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:222) 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:1225) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:775) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:457) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:139) at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:172) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:928) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1025) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:908) 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:453) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306) 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:166) 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:1691) Caused by: com.ibm.rdm.fronting.server.exception.BadRequestException: Propagated exception; original message [com.ibm.rdm.fronting.server.exception.BadRequestException] at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:178) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:649) at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:653) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.checkError(InternalServiceExchange.java:53) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.getResponse(InternalServiceExchange.java:37) at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.executeServiceRequest(CoreServiceRequest.java:56) 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:628) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:324) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.executeRequestSequences(InternalCoreServices.java:1008) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleRequestSequences(InternalCoreServices.java:847) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:319) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:248) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:234) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalBaseServiceRequest.executeRequestSequence(InternalBaseServiceRequest.java:114) ... 47 more Caused by: com.ibm.rdm.fronting.server.exception.BadRequestException: com.ibm.rdm.fronting.server.exception.BadRequestException at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:178) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:163) 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:594) 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:707) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:322) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:248) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:234) at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.executeServiceRequest(CoreServiceRequest.java:54) ... 64 more Request PUT https://bt-clmtestserver01.hqs.sbt.siemens.com/jts/storage/com.ibm.rdm.userPreferences/baea3e583a0458587fcca1dfa73d7b47 HTTP/1.1 If-Match: * Content-Type: application/rdf+xml Authorization: OAuth oauth_token_secret="NGCkBIcGtUpWKlSYKTlgwCFl2DFyU1QG1e5mO2M", oauth_nonce="1040393101309457463", oauth_token="e37564f713ca428fab457c8b3a7dfbd5", oauth_consumer_key="4b1ba86ce43d43349143de0fb6c46b31", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1372191990", oauth_version="1.0", oauth_signature="1fnLT35EsR%2BPRu6HTRtNB3bAAHg%3D" --Start entity--- --End entity----- Response: HTTP/1.1 400 Date: Tue, 25 Jun 2013 20:26:30 GMT X-Powered-By: Servlet/3.0 $WSEP: Connection: close Content-Type: text/html;charset=UTF-8 Content-Language: en-US Content-Length: 60 ---Start entity--- Error 400: CRJZS5318E Modified by user header must be set. --End entity------ 2013-06-25 22:26:30,896 [ RM-Task-Executor-1] ERROR rvices.configure.internal.ConfigureServiceInternal - CRRRS9601E The storage area com.ibm.rdm.locks could not be created. 2013-06-25 22:26:30,912 [ RM-Task-Executor-1] ERROR erver.services.locks.internal.LockResourceUpgrader - Errors upgrating lock resources java.lang.RuntimeException: java.lang.Exception: CRRRS9601E The storage area com.ibm.rdm.locks could not be created. at com.google.common.base.Throwables.propagate(Throwables.java:160) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgradeExistingData(LockResourceUpgrader.java:141) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgrade(LockResourceUpgrader.java:61) at com.ibm.rdm.fronting.server.services.locks.internal.LockServiceInitializer.execute(LockServiceInitializer.java:72) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:68) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:1) at com.ibm.rdm.fronting.server.concurrent.RRSConcurrency$1$1.call(RRSConcurrency.java:132) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:773) Caused by: java.lang.Exception: CRRRS9601E The storage area com.ibm.rdm.locks could not be created. at com.ibm.rdm.fronting.server.config.namespace.NamespaceUtil.createNamespace(NamespaceUtil.java:114) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgradeExistingData(LockResourceUpgrader.java:139) ... 10 more 2013-06-25 22:26:30,912 [ RM-Task-Executor-1] ERROR erver.services.locks.internal.LockResourceUpgrader - Some existing locks couldn't be upgraded. The are printed here for reference. They will no longer be available. java.lang.RuntimeException: java.lang.Exception: CRRRS9601E The storage area com.ibm.rdm.locks could not be created. at com.google.common.base.Throwables.propagate(Throwables.java:160) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgradeExistingData(LockResourceUpgrader.java:141) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgrade(LockResourceUpgrader.java:61) at com.ibm.rdm.fronting.server.services.locks.internal.LockServiceInitializer.execute(LockServiceInitializer.java:72) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:68) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:1) at com.ibm.rdm.fronting.server.concurrent.RRSConcurrency$1$1.call(RRSConcurrency.java:132) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:773) Caused by: java.lang.Exception: CRRRS9601E The storage area com.ibm.rdm.locks could not be created. at com.ibm.rdm.fronting.server.config.namespace.NamespaceUtil.createNamespace(NamespaceUtil.java:114) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgradeExistingData(LockResourceUpgrader.java:139) ... 10 more 2013-06-25 22:26:30,912 [ RM-Task-Executor-1] INFO erver.services.locks.internal.LockResourceUpgrader - <rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rm="http://www.ibm.com/xmlns/rdm/rdf/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <rm:Lock rdf:about="https://bt-clmtestserver01.hqs.sbt.siemens.com/rm/resources/_8Dng6dffEeKO6uEeMD0zMA"> <dcterms:identifier rdf:resource="https://bt-clmtestserver01.hqs.sbt.siemens.com/rm/locks/_8Dng6dffEeKO6uEeMD0zMA"/> <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime" >2013-06-18T06:28:20.131Z</dcterms:created> <dcterms:creator rdf:resource="https://bt-clmtestserver01.hqs.sbt.siemens.com/jts/users/erwin.kunz%40siemens.com"/> <rm:persistent rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean" >true</rm:persistent> </rm:Lock> </rdf:RDF> ============ 2013-06-25 22:26:30,912 [ RM-Task-Executor-1] INFO erver.services.locks.internal.LockResourceUpgrader - Creating/updating version identifier to: 1 2013-06-25 22:26:30,974 [ RM-Task-Executor-1] ERROR ing.server.core.tasks.internal.InternalTaskManager - Uncaught exception while executing task com.ibm.rdm.fronting.server.exception.BadRequestException: Propagated exception; original message [com.ibm.rdm.fronting.server.exception.BadRequestException] at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:178) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:649) at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:653) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.checkError(InternalServiceExchange.java:53) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.getResponse(InternalServiceExchange.java:37) at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.executeServiceRequest(CoreServiceRequest.java:56) at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:110) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.createVersionResource(LockResourceUpgrader.java:117) at com.ibm.rdm.fronting.server.services.locks.internal.LockResourceUpgrader.upgrade(LockResourceUpgrader.java:78) at com.ibm.rdm.fronting.server.services.locks.internal.LockServiceInitializer.execute(LockServiceInitializer.java:72) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:68) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:1) at com.ibm.rdm.fronting.server.concurrent.RRSConcurrency$1$1.call(RRSConcurrency.java:132) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:773) Caused by: com.ibm.rdm.fronting.server.exception.BadRequestException: com.ibm.rdm.fronting.server.exception.BadRequestException at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:178) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:163) 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:594) 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:707) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:322) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:248) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:234) at com.ibm.rdm.fronting.server.core.jpi.internal.CoreServiceRequest.executeServiceRequest(CoreServiceRequest.java:54) ... 12 more Request POST https://bt-clmtestserver01.hqs.sbt.siemens.com/jts/storage/com.ibm.rdm.locks HTTP/1.1 Name: version Content-Type: text/plain Authorization: OAuth oauth_token_secret="", oauth_nonce="-4313570516841052718", oauth_token="", oauth_consumer_key="4b1ba86ce43d43349143de0fb6c46b31", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1372191990", oauth_version="1.0", oauth_signature="RoZ1T0sbiAN8UP%2FlFm%2BQ7iya4pc%3D" --Start entity--- --End entity----- Response: HTTP/1.1 400 Date: Tue, 25 Jun 2013 20:26:30 GMT X-Powered-By: Servlet/3.0 $WSEP: Connection: close Content-Type: text/html;charset=UTF-8 Content-Language: en-US Content-Length: 93 ---Start entity--- Error 400: CRJZS5328E Creator must be specified while posting a resource in the import mode --End entity------ 2013-06-25 22:26:37,023 [ RM-Command-Executor-1] INFO rvices.configure.internal.ConfigureServiceInternal - CRRRS9622I Image resources were created. 2013-06-25 22:26:37,023 [ RM-Command-Executor-1] INFO rvices.configure.internal.ConfigureServiceInternal - CRRRS9622I Content Type Handler resources were created. 2013-06-25 22:26:37,132 [ RM-Command-Executor-1] INFO rvices.configure.internal.ConfigureServiceInternal - CRRRS9622I Configurations resources were created. 2013-06-25 22:26:37,132 [ RM-Command-Executor-1] INFO rvices.configure.internal.ConfigureServiceInternal - CRRRS9622I Listeners resources were created. 2013-06-25 22:26:38,648 [ RM-storageAreaExecutor-1] INFO nting.server.rrs.migration.MigrationProgressRecord - CRRRS8012I Migrating storage area: com.ibm.rdm.types 2013-06-25 22:26:40,164 [RM-TransformationTaskService-1] INFO nting.server.rrs.migration.MigrationProgressRecord - CRRRS8013I Processed resource {com.ibm.rdm.types}_L4i24N-tEeCoG7xjPLuf0g revision: _L4tO8N-tEeCoG7xjPLuf0g |
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
Guido, did you do the online upgrade after upgrading RM? If you did, please check if there are errors in the log. Also, please consider to open a PMR.
I would also check to make sure all appropriate licenses are still assigned, including those of the rm_user.
I run the repotool upgrade, the migration UI and the inizialize command.
Afterwards I rebooted.
The migration cam with an error, telling me something went wrong, but not important. After the reboot, If I run now the migration UI, it tells me there is no upgrade necessary. Also in the home button menu i see all PA's, what I do not if the migration was not run.
One word about the rm_internal license. I run now three upgrades from 402 to 403. Everytime the rm_internal license, rm_collector and trs were not available after starting first time. I had to load them manually by downloading the jar file and add it in the license manager. This is very unstable.
I also stopped everything removed again temp and wstemp in the profile. But it was not helping.
Next step will be to complettly remove rm (it's an own profile, so I can easly just remove rm), and reinstall. Just to be sure it's only in the DB.
I will create also a PMR, but I need a solution urgently and PMR's needs weeks for a good answer.
Any idea what the
Error 403: CRJZS0040E There is no REST service handler registered for the path "/undefined".
means?
I do not see more errors in the logs than the one reported in the question above.
I don't think that message is particularly meaningful. It's basically just saying that there's no handler for a request to "/undefined" which isn't surprising. The real question is how/why did the path get constructed to start with "/undefined". It may have simply resulted downstream from the "Lock not found" exception coming from AcquireLockRequest, but the trace doesn't provide much in the way of clues of what is happening here.
One thing I would be curious about though is what error occurred during migration that was not "important"?
The truth is this is why we recommend the PMR process. It may seem these can take a long time, but sometimes it's because these aren't simple problems and require a lot of understanding and investigation - something that could certainly be difficult to achieve in a forum post. Nonetheless I'll try to dig around and see what might cause the "Lock not found" problem since it's our best clue at the moment.
Thank you.
PMR created: 58918 113 848
Found interesting error happened during migration (maybe the one mentioned as "not important").
I put it into answer because of number of characters.
Yes, this pretty much confirmed what the development team suspected. That migration was only partially successful and did not update the lock graphs to the new format.
I'll try to get more details about how this can happen and what can be done about it (ie, will migration have to be performed again or can this be repaired in a post migration environment).
That said, at this point I'd prefer to continue the investigation and discussion through the PMR. Thank you for opening that.