How do I exit the state CRRRS5730E Server requires configuration ?
Hi,
I am upgrading CLM from 3.0.1.6 to 4.0.7.
I have ran the upgrade script "upgrade/rm/rm_upgrade.sh", started my WAS server and went to https://hostname.example.com:port/rm/web/projects/migration to start the migration.
Now, when I try to access RM application, I have following logs :
2018-01-17 18:01:31,784 [ WebContainer : 9] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9909I The version of this build is: R
MS407X, the version of current repository is: RMS407X, upgrade is required: false
2018-01-17 18:01:31,784 [ WebContainer : 9] INFO ing.server.core.repository.RepositoryAccessManager - MigrationState: MIGRATION_NOT_RUNNING
2018-01-17 18:01:31,784 [ WebContainer : 9] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9908I Repository state changed from I
NITIALIZING to REQUIRES_CONFIGURATION
2018-01-17 18:01:31,788 [ WebContainer : 9] ERROR er.services.servicedocument.ServiceDocumentService - Server Error: Entry [99dc6d7c9260ad4c]
com.ibm.rdm.fronting.server.exception.ServiceUnavailableException: CRRRS5730E Server requires configuration
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:256)
at com.ibm.rdm.fronting.server.exception.RRSException.newServiceUnavailableException(RRSException.java:86)
at com.ibm.rdm.fronting.server.core.repository.RepositoryAccessManager.makeErrorResponse(RepositoryAccessManager.java:438)
at com.ibm.rdm.fronting.server.services.RMRestService.checkRepositoryState(RMRestService.java:662)
at com.ibm.rdm.fronting.server.services.RMRestService.performService(RMRestService.java:324)
at com.ibm.rdm.fronting.server.services.RMRestServiceBase.service(RMRestServiceBase.java:206)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:159)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:285)
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:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1233)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:782)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
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:165)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
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:967)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3980)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1016)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1820)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
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:1892)
Request
--Not Provided--
Response
--Not Provided--
I don't know what configuration is necessary.
Any help will be welcome.
3 answers
Hi Laurent,
Thanks for your answer.
When I go to the setup, I can Finalize the setup for RM application. But it gives me an error :
Error 500: Internal Server Error
com.ibm.rdm.fronting.server.exception.InternalServerErrorException (More info found at entry [ba175c395c8f6d3c] in the RM application server log)
Requirements Management/4.0.7
When I go to the logs, I see those traces :
2018-01-24 17:16:24,821 [ WebContainer : 12] ERROR ronting.server.services.configure.ConfigureService - CRRRS9609W The template "{0}" was not crea
ted. Detailed message: {1}
2018-01-24 17:16:24,850 [ WebContainer : 12] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9909I The version of this build is: R
MS407X, the version of current repository is: RMS407X, upgrade is required: false
2018-01-24 17:16:24,851 [ WebContainer : 12] INFO ing.server.core.repository.RepositoryAccessManager - MigrationState: MIGRATION_NOT_RUNNING
2018-01-24 17:16:24,894 [ WebContainer : 12] ERROR ronting.server.services.configure.ConfigureService - Server Error: Entry [ba175c395c8f6d3c]
com.ibm.rdm.fronting.server.exception.InternalServerErrorException: Propagated exception; original message [com.ibm.rdm.fronting.server.exception.InternalServer
ErrorException]
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:220)
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:737)
at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:741)
[...]
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:220)
at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:180)
at com.ibm.rdm.fronting.server.core.jpi.internal.ServiceResponseHandler.statusCheck(ServiceResponseHandler.java:142)
[...]
IServiceRequests
RestClient.POST
Request
POST https://myhost/jts/process/templates?overwrite=true HTTP/1.1
Authorization: OAuth oauth_token_secret="", oauth_nonce="7035350389304427099", oauth_token="", oauth_consumer_key="ERASED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1516810584", oauth_version="1.0", oauth_signature="kMN7%2Fju5gNX7ZSGtZQN8rZy%2BlnI%3D"
--Start entity---
--End entity-----
Response:
HTTP/1.1 500
Date: Wed, 24 Jan 2018 16:16:24 GMT
X-Powered-By: Servlet/3.0
Connection: close
Content-Type: text/plain;charset=UTF-8
Content-Language: en-US
Content-Length: 14679
---Start entity---
Error 500
com.ibm.team.repository.common.TeamRepositoryException: The user "ADMIN" does not exist in the database
at com.ibm.team.process.internal.authoring.service.ProcessDefinitionImportParticipantService.importProcessDescription(ProcessDefinitionImportParticipantService.java:136)
at com.ibm.team.process.internal.authoring.service.ProcessDefinitionImportParticipantService.importParticipantUncommitted(ProcessDefinitionImportParticipantService.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[...]
Caused by: com.ibm.team.process.internal.authoring.common.utils.ProcessAuthoringException: The user "ADMIN" does not exist in the database
at com.ibm.team.process.internal.authoring.service.utils.JfsClientFactory.createJfsClient(JfsClientFactory.java:48)
at com.ibm.team.process.internal.authoring.service.utils.TemplateProcessDescriptionHelper.<init>(TemplateProcessDescriptionHelper.java:288)
[...]
Caused by: com.ibm.team.repository.common.TeamRepositoryException: The user "ADMIN" does not exist in the database
at com.ibm.team.process.internal.authoring.service.utils.LocalOAuthEnabledHttpClient.acquireAccessToken(LocalOAuthEnabledHttpClient.java:155)
at com.ibm.team.process.internal.authoring.service.utils.LocalOAuthEnabledHttpClient.<init>(LocalOAuthEnabledHttpClient.java:189)
at com.ibm.team.process.internal.authoring.service.utils.ProcessAuthoringJfsClient.<init>(ProcessAuthoringJfsClient.java:256)
[...]
Caused by: net.oauth.OAuthException: The user "ADMIN" does not exist in the database
at com.ibm.team.repository.service.internal.oauth.OAuthServiceProvider.runAsUser(OAuthServiceProvider.java:2165)
at com.ibm.team.repository.service.internal.oauth.OAuthServiceProvider.getAccessToken(OAuthServiceProvider.java:1809)
[...]
--End entity------
Hi,
I wanted to post an update as we have finally found the answer to the problem.
The message saying "The user "ADMIN" does not exist in the database" was the key to the solution. I don't know how nor when, but in CLM 3.0.1, we had a user (let's say John Smith), that was bound to the ADMIN user. When I logged into JTS using "ADMIN" login, I was identified as the user "John Smith". But the id of this user was not "ADMIN", it was "JS".
To resolve the problem, we had to modify the "JS" id to "ADMIN". After that, we were able to finish the RM setup after the migration to CLM 4.0.7.