DOORS NG 6.0.3 corrupt projects "Loading artifacts page..."
We are seeing an issue where RM 6.0.3 Projects created by created by going to rm/admin#action=com.ibm.team.process.manageProjectAreas and clicking "Create Project Area" will result in a corrupt project area. Attempting to "Explore the Project" and click "Artifacts" within this corrupt project area will cause the browser to hang and display "Loading artifacts page..." indefinitely. The rm.log log shows that during the project creation it displays: 2017-03-03 17:55:37,578 [rm: AsynchronousTaskRunner-2 @@ 17:55] WARN g.server.services.vvc.JAFConfigurationCacheService - Could not get Components for context https://doorsng603.clm.ibmcloud.com/rm/process/project-areas/_m1JhYAA6EeeWgtL21G2zyQ (JAF returned null). The project may have been corrupted at creation time 2017-03-03 17:55:37,662 [ RM-Task-Executor-41539] ERROR ing.server.core.tasks.internal.InternalTaskManager - Uncaught exception while executing task Init component resources com.ibm.rdm.fronting.server.exception.InternalServerErrorException: Propagated exception; original message [InternalServerErrorException: com.ibm.rdm.fronting.server.exception.InternalServerErrorException] at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:266) at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:800) at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:804) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.checkError(InternalServiceExchange.java:54) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalServiceExchange.getResponse(InternalServiceExchange.java:37) at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:118) at com.ibm.rdm.fronting.server.services.configure.RMResourcesUtil.createResources(RMResourcesUtil.java:365) at com.ibm.rdm.fronting.server.services.configure.RMResourcesUtil.createResourcesFromDirectory(RMResourcesUtil.java:146) at com.ibm.rdm.fronting.server.services.process.internal.WellKnownTypeUtil.createProjectResources(WellKnownTypeUtil.java:144) at com.ibm.rdm.fronting.server.services.process.internal.WellKnownTypeUtil.addWellKnownTypes(WellKnownTypeUtil.java:87) at com.ibm.rdm.fronting.server.rrs.vvcproxy.components.internal.RMComponentService$2.execute(RMComponentService.java:672) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:124) at com.ibm.rdm.fronting.server.core.tasks.internal.InternalTaskManager$Executor.call(InternalTaskManager.java:1) at com.ibm.rdm.fronting.server.concurrent.RMForwardingListeningExecutorService$1.call(RMForwardingListeningExecutorService.java:61) at java.util.concurrent.FutureTask.run(FutureTask.java:274) at com.ibm.rdm.fronting.server.concurrent.RMListenableFutureTask.run(RMListenableFutureTask.java:68) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627) at java.lang.Thread.run(Thread.java:809) Caused by: com.ibm.rdm.fronting.server.exception.InternalServerErrorException: com.ibm.rdm.fronting.server.exception.InternalServerErrorException at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:266) at com.ibm.rdm.fronting.server.exception.RRSException.newInternalServerErrorException(RRSException.java:152) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.wrapException(JAFStorageService.java:632) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.handleException(JAFStorageService.java:645) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.doCreate(JAFStorageService.java:291) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.doExecute(JAFStorageService.java:107) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.access$0(JAFStorageService.java:100) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService$1.run(JAFStorageService.java:91) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService$1.run(JAFStorageService.java:1) at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:254) at com.ibm.rdm.fronting.server.core.TeamServiceContextUtil.runAsAdmin(TeamServiceContextUtil.java:32) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.executeServiceRequest(JAFStorageService.java:88) at com.ibm.rdm.fronting.server.core.spi.JAFServiceRequest.executeServiceRequest(JAFServiceRequest.java:27) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalDefaultPartitionerFactory$1ExecuteServiceRequest.call(InternalDefaultPartitionerFactory.java:29) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalDefaultPartitionerFactory$1ExecuteServiceRequest.call(InternalDefaultPartitionerFactory.java:1) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFBulkPartitionerFactory.handleNonBulkRequests(JAFBulkPartitionerFactory.java:289) at com.ibm.rdm.fronting.server.core.jpi.internal.OrdinaryBulkPartitionerFactory.execute(OrdinaryBulkPartitionerFactory.java:70) at com.ibm.rdm.fronting.server.core.jpi.internal.OrdinaryBulkPartitionerFactory$1OrdinaryBulkPartition$1.run(OrdinaryBulkPartitionerFactory.java:51) at com.ibm.rdm.fronting.server.core.jpi.internal.OrdinaryBulkPartitionerFactory$1OrdinaryBulkPartition$1.run(OrdinaryBulkPartitionerFactory.java:1) at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:254) at com.ibm.rdm.fronting.server.core.TeamServiceContextUtil.runAsAdmin(TeamServiceContextUtil.java:32) at com.ibm.rdm.fronting.server.core.jpi.internal.OrdinaryBulkPartitionerFactory$1OrdinaryBulkPartition.call(OrdinaryBulkPartitionerFactory.java:46) at com.ibm.rdm.fronting.server.core.jpi.internal.OrdinaryBulkPartitionerFactory$1OrdinaryBulkPartition.call(OrdinaryBulkPartitionerFactory.java:1) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleExecutables(InternalCoreServices.java:711) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:408) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.executeRequestSequences(InternalCoreServices.java:1142) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.handleRequestSequences(InternalCoreServices.java:1090) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:363) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:259) at com.ibm.rdm.fronting.server.core.jpi.internal.InternalCoreServices.execute(InternalCoreServices.java:252) at com.ibm.rdm.fronting.server.core.spi.BaseServiceRequest.execute(BaseServiceRequest.java:112) ... 13 more Caused by: com.ibm.team.jfs.sdk.common.InternalServerErrorException: https://doorsng603.clm.ibmcloud.com/rm/cm/component/_m5GNQAA6EeeWgtL21G2zyQ at com.ibm.team.jfs.sdk.storage.internal.StorageService.getComponentId(StorageService.java:2201) at com.ibm.team.jfs.sdk.storage.internal.StorageService.setComponentUri(StorageService.java:2191) at com.ibm.team.jfs.sdk.storage.internal.Resource.setComponentUri(Resource.java:536) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.setComponentFromParams(JAFStorageService.java:512) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.prepareForCreate(JAFStorageService.java:491) at com.ibm.rdm.fronting.server.core.jpi.internal.JAFStorageService.doCreate(JAFStorageService.java:280) ... 39 more Caused by: com.ibm.team.repository.common.ItemNotFoundException: https://doorsng603.clm.ibmcloud.com/rm/cm/component/_m5GNQAA6EeeWgtL21G2zyQ at com.ibm.team.repository.service.vvc.sdk.internal.FoundationVVCConfigurationManager.getComponentByUri(FoundationVVCConfigurationManager.java:2776) at sun.reflect.GeneratedMethodAccessor1789.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy3636.getComponentByUri(Unknown Source) at com.ibm.team.jfs.sdk.storage.internal.StorageService.getComponentId(StorageService.java:2198) ... 44 more Request --Not Provided-- Response --Not Provided--
This issue can be avoided by creating a project area by going to the jts/admin and clicking the "Create Project Area" link under "Requirements Management" application. This wizard will issue a POST to rm/projects instead of rm/service/com.ibm.team.process.internal.service.web.IProcessWebUIService/projectArea.
We are using CLM 6.0.3 ifix2 on Liberty Profile with DB2 10.5.0.6 on RHEL Linux 6.8. We have multiple deployments - upgraded or fresh - that are impacted.
|
Accepted answer
I think it is a known Benjamin Chodroff selected this answer as the correct answer
Comments
Benjamin Chodroff
commented May 25 '17, 4:23 p.m.
Agree, this appears to be the cause. We ended up getting a hotfix from support. |
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
You should consider approaching Support