Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Why will RM not register after restoring server?

Questions
Tags
Users
Badges
Jeff Peters
(11●1) Jun 02 '17, 10:36 a.m.

 We lost our RTC application server and had to restore from an older backup.  Database server was restored from a current backup.  After changing paths to db server in all teamserver.properties files, I ran /jts/setup with Custom Setup selected.  All the settings tested fine, and all the applications showed as registered, except RM, which showed up in the Applications to Register box.  When the Register Applications button was pressed to register RM, it threw the following error: 

Request to service https://rtc.the-inet.com/rm/configureRegistration failed with status code 400 and response body: CRRRS9639E The application registration handler could not save the configuration. The detailed error message is: com.ibm.rdm.fronting.server.exception.ForbiddenException: Propagated exception; original message [com.ibm.rdm.fronting.server.exception.ForbiddenException]
com.ibm.team.repository.common.TeamRepositoryException
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.checkHttpResponse(FriendsAdminRestService.java:820)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:468)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:1)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:945)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:910)
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.executeHttpRequest(FriendsAdminRestService.java:772)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.notifyAppRegistrationHandler(ApplicationRegistrationFriendRestService.java:361)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.postRegisterApp(ApplicationRegistrationFriendRestService.java:201)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
com.sun.proxy.$Proxy418.postRegisterApp(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:530)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2359)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2153)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1963)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
java.lang.Thread.run(Thread.java:761)


</pre>
<div>
    I have not been able to locate any information on what might be the root of the problem, or how it might be fixed. Any assistance would be greatly appreciated.
</div>

0 votes

Comments
Jeff Peters
Jun 02 '17, 10:51 a.m.
Version is 4.0.6 on Windows Server 2008 R2; DB is MSSQL on Windows Server 2016.

Donald Nong
Jun 05 '17, 3:42 a.m.
Have you checked the rm.log file and see what it says there?

Jeff Peters
Jun 05 '17, 3:54 p.m.
Donald:  rm.log says the server is getting a 403 error when trying to talk to itself.  Specifically, the URL https://oursever/jts/storage/com.ibm.rdm.project-resources/configure If I manually go to that URL, it kicks back to the JTS login.  All the applications other than rm have registered without a problem.

Donald Nong
Jun 05 '17, 10:01 p.m.
A proper restore should not require running /jts/setup again. Something must have gone wrong during the process. If you have to recover from the current state, I suggest you contact Support and see what options you have.

2 answers
4,301 views
0 votes

2 answers

Permanent link
Krunal Gaoli
(67●12●69) Jun 02 '17, 3:56 p.m.

1.Please check for indices too. Map respective indices in conf/indices location.

2. Check whether your rm_users is archive ?
3. Recheck database connection team.server. property file 

0 votes

Comments
Jeff Peters
Jun 02 '17, 4:12 p.m.
  Thanks for the reply, Krunal. 1. There are indices folders in the following:  \server\conf\qm\indices \server\conf\jts\indices \server\conf\ccm\indices \server\conf\rm\setup\indices The rm\setup\indices folder only has XML files in it; there doesn't appear to be anything to do there. The other 3 indices folders have folders with generated names, and a workitemindex folder. How should these be mapped? 2. There is no rm_users file or folder anywhere in our JazzTeamServer file tree. 3. All database connections have been checked and re-checked in all teamserver.properties files. Can you give me more information on 1. and 2.? Thanks, - Jeff

Permanent link
Krunal Gaoli
(67●12●69) Jun 02 '17, 4:30 p.m.

 Hi Jeff,


1 Copy the indices of crashed rm into new \server.conf\rm\setup\indices.
2. By default jts provides each user for each application user e.g. ccm_users. qm_user, etc.
login in JTS/admin page check for active users. In active users list check for rm_users is there or not.

Best Regards
Krunal
krunalgaoli@gmail.com.

0 votes

Comments
Jeff Peters
Jun 02 '17, 5:19 p.m.
 1. is a problem; we do not have access to any recent data from the crashed app server. The files that are on the restored server are from the original backup from when the app server was first configured 2 years ago. 2. There is a user called rm_user in the Active Users list. - Jeff

Your answer

Register or log in to post 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jun 02 '17, 10:36 a.m.

Question was seen: 4,301 times

Last updated: Jun 05 '17, 10:01 p.m.

Confirmation Cancel Confirm