RQM 3.0.1: Sample project creation failing...
Hi all,
An RTC 3.0 instance has been migrated to RTC 3.0.1 on a Windows 2008 box and, after running the usual /jts/setup through, everything looked fine. This RTC instance was then reconfigured to be started up as a Windows service but in process of doing so the "Maximum memory pool" value has erroneously been left on its default value (256MB if I'm not mistaken). The RTC instance was then started up and we attempted to create the sample Lifecycle Project ("JKE Banking"). This attempt resulted with java.lang.OutOfMemoryError for JTS, RM and QM components. The "Maximum memory pool" parameter was subsequently fixed, RTC instance restarted and everything seemed fine again, all existing CCM projects were available and all data was seemingly there.
However, when we try to create the "JKE Banking" Lifecycle Project now, we're getting the following exception in the RM log:
2011-08-18 16:39:00,167 ERROR dm.fronting.server.services.process.ProjectService - Server Error: Entry
com.ibm.rdm.fronting.server.exception.UnexpectedResponseException: CRRRS1008E JTS internal error
at com.ibm.rdm.fronting.server.exception.RRSException.newUnexpectedResponseException(RRSException.java:47)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.sendHttpRequest(HttpClientWrapperService.java:716)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.createContent(HttpClientWrapperService.java:605)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.postResource(HttpClientWrapperService.java:311)
at com.ibm.rdm.fronting.server.services.process.internal.ProjectServiceInternal.doPostInternal(ProjectServiceInternal.java:155)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:342)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:275)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:96)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:149)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:152)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:295)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:811)
Request
POST https://my.box.com:9443/jts/process/project-areas HTTP/1.1
X-Jazz-Query-Timeout: -1
Authorization: OAuth oauth_token_secret="m%2BX9md4sU%2F%2FZX%2Fp1f9KiyEclFUpU83oHc0vgcGLs38o%3D", oauth_nonce="4377393228449099573", oauth_token="e1af9fc84f4a4126917622b83e38fbe9", oauth_consumer_key="839805f667b1405b8b425039c2fdc79c", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1313685540", oauth_version="1.0", oauth_signature="5jhBkNOgR4UQaa5w%2BAvrqxAHgBk%3D"
--Start entity---
<xml><jp06>
<jp06>JKE Banking (Requirements)</jp06>
<jp06>The purpose of this project is to specify and manage the requirements of the JKE Business Recovery Matters project.</jp06>
<jp06>
<members><member><user>https://my.box.com:9443/jts/conkask</user></member></members></jp06>
--End entity-----
Response:
HTTP/1.1 500
Content-Type: text/plain;charset=UTF-8
Content-Length: 12486
---Start entity---
Error 500
Another project area with the name 'JKE Banking (Requirements)' already exists
com.ibm.team.process.common.service.ProcessDataValidationException: Another project area with the name 'JKE Banking (Requirements)' already exists
at com.ibm.team.process.internal.service.ProcessService.validateUniqueProjectAreaName(ProcessService.java:2610)
at com.ibm.team.process.internal.service.ProcessService.validateProjectAreaPreSave(ProcessService.java:2480)
at com.ibm.team.process.internal.service.ProcessService.validatePreSave(ProcessService.java:1978)
at com.ibm.team.process.internal.service.ProcessService.doSaveProcessItemsWithOverride(ProcessService.java:929)
at com.ibm.team.process.internal.service.ProcessService$1.run(ProcessService.java:869)
at com.ibm.team.repository.service.internal.TransactionService$2.run(TransactionService.java:204)
at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:458)
at com.ibm.team.repository.service.internal.rdb.RepositoryData
--End entity------
I've been through all Project Areas and can't find this project anywhere, neither in active nor in archived projects. I managed to create a new Lifecycle Project (with artefacts in CCM, QM and RM) though, therefore I presume that notwithstanding the previous OutOfMemory exceptions the databases are consistent. All underlying databases are Derby.
Is there any workaround for this? Alternatively, the only valuable data on the system is currently in CCM, is there a way to reinitialise the RM database?
Regards,
Kristijan
An RTC 3.0 instance has been migrated to RTC 3.0.1 on a Windows 2008 box and, after running the usual /jts/setup through, everything looked fine. This RTC instance was then reconfigured to be started up as a Windows service but in process of doing so the "Maximum memory pool" value has erroneously been left on its default value (256MB if I'm not mistaken). The RTC instance was then started up and we attempted to create the sample Lifecycle Project ("JKE Banking"). This attempt resulted with java.lang.OutOfMemoryError for JTS, RM and QM components. The "Maximum memory pool" parameter was subsequently fixed, RTC instance restarted and everything seemed fine again, all existing CCM projects were available and all data was seemingly there.
However, when we try to create the "JKE Banking" Lifecycle Project now, we're getting the following exception in the RM log:
2011-08-18 16:39:00,167 ERROR dm.fronting.server.services.process.ProjectService - Server Error: Entry
com.ibm.rdm.fronting.server.exception.UnexpectedResponseException: CRRRS1008E JTS internal error
at com.ibm.rdm.fronting.server.exception.RRSException.newUnexpectedResponseException(RRSException.java:47)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.sendHttpRequest(HttpClientWrapperService.java:716)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.createContent(HttpClientWrapperService.java:605)
at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.postResource(HttpClientWrapperService.java:311)
at com.ibm.rdm.fronting.server.services.process.internal.ProjectServiceInternal.doPostInternal(ProjectServiceInternal.java:155)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:342)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:275)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:96)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:149)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:152)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:295)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:811)
Request
POST https://my.box.com:9443/jts/process/project-areas HTTP/1.1
X-Jazz-Query-Timeout: -1
Authorization: OAuth oauth_token_secret="m%2BX9md4sU%2F%2FZX%2Fp1f9KiyEclFUpU83oHc0vgcGLs38o%3D", oauth_nonce="4377393228449099573", oauth_token="e1af9fc84f4a4126917622b83e38fbe9", oauth_consumer_key="839805f667b1405b8b425039c2fdc79c", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1313685540", oauth_version="1.0", oauth_signature="5jhBkNOgR4UQaa5w%2BAvrqxAHgBk%3D"
--Start entity---
<xml><jp06>
<jp06>JKE Banking (Requirements)</jp06>
<jp06>The purpose of this project is to specify and manage the requirements of the JKE Business Recovery Matters project.</jp06>
<jp06>
<members><member><user>https://my.box.com:9443/jts/conkask</user></member></members></jp06>
--End entity-----
Response:
HTTP/1.1 500
Content-Type: text/plain;charset=UTF-8
Content-Length: 12486
---Start entity---
Error 500
Another project area with the name 'JKE Banking (Requirements)' already exists
com.ibm.team.process.common.service.ProcessDataValidationException: Another project area with the name 'JKE Banking (Requirements)' already exists
at com.ibm.team.process.internal.service.ProcessService.validateUniqueProjectAreaName(ProcessService.java:2610)
at com.ibm.team.process.internal.service.ProcessService.validateProjectAreaPreSave(ProcessService.java:2480)
at com.ibm.team.process.internal.service.ProcessService.validatePreSave(ProcessService.java:1978)
at com.ibm.team.process.internal.service.ProcessService.doSaveProcessItemsWithOverride(ProcessService.java:929)
at com.ibm.team.process.internal.service.ProcessService$1.run(ProcessService.java:869)
at com.ibm.team.repository.service.internal.TransactionService$2.run(TransactionService.java:204)
at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:458)
at com.ibm.team.repository.service.internal.rdb.RepositoryData
--End entity------
I've been through all Project Areas and can't find this project anywhere, neither in active nor in archived projects. I managed to create a new Lifecycle Project (with artefacts in CCM, QM and RM) though, therefore I presume that notwithstanding the previous OutOfMemory exceptions the databases are consistent. All underlying databases are Derby.
Is there any workaround for this? Alternatively, the only valuable data on the system is currently in CCM, is there a way to reinitialise the RM database?
Regards,
Kristijan
One answer
Hi,
dependent on which products you installed the sample project (which is suggested to be only deployed in a test server) will create several projects.
If that fails, you should check all applications for a JKE* project. Rename those projects and the archive them. Maybe your project is archived?
If not you might have as strange case where the repository thinks the project is there, but does not show it, due to the out of mem error you mention. In such a case you might want to reach out to support or create a work item.
There slao is a database validation option in the repotools you could try out.
dependent on which products you installed the sample project (which is suggested to be only deployed in a test server) will create several projects.
If that fails, you should check all applications for a JKE* project. Rename those projects and the archive them. Maybe your project is archived?
If not you might have as strange case where the repository thinks the project is there, but does not show it, due to the out of mem error you mention. In such a case you might want to reach out to support or create a work item.
There slao is a database validation option in the repotools you could try out.