CRRRS3008E & CRJCA0028I errors when finalizing RM application install
Trying to install CLM 4.0.2 on Windows 2008 server with an SQL server DB, using Tomcat.
The admin log file just says: "CRJCA0028I Initialization of the Lifecycle Project Administration Application failed. Please register the Lifecycle Project Administration application with the Jazz Team Server."
4 answers
Last error on the RM log was:
2013-05-30 17:25:07,996 [ http-bio-9443-exec-42] ERROR er.services.servicedocument.ProjectResourceService - Server Error: Entry [d725ffe5c566a300]
java.lang.IllegalArgumentException: OAuthConsumerProperties must not be null
Hi Bas, yes, I've checked that.
The most common errors (and they appear as I'm trying to configure RM again and again) are:
1. 2013-08-27 18:58:17,871 [ http-bio-9443-exec-36] WARN ver.core.oauth.internal.OauthAuthenticationService - CRRRS01903E An authorization exception occurred while the principal was being retrieved.
java.lang.NullPointerException
at com.ibm.rdm.fronting.server.core.oauth.internal.OauthAuthenticationService.getAuthorizationPrincipalFromRequest(OauthAuthenticationService.java:130)
at com.ibm.rdm.fronting.server.core.oauth.internal.OauthAuthenticationService.requiresAuthorization(OauthAuthenticationService.java:87)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:369)
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:722)
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:722)
2. 2013-08-27 18:58:17,872 [ http-bio-9443-exec-36] ERROR er.services.servicedocument.ProjectResourceService - Server Error: Entry [545b411d44016914]
java.lang.IllegalArgumentException: OAuthConsumerProperties must not be null
at com.ibm.team.jfs.app.oauth.OAuthHelper.validateConsumer(OAuthHelper.java:2302)
at com.ibm.team.jfs.app.oauth.OAuthHelper.getRequestTokenFromProvider(OAuthHelper.java:1010)
at com.ibm.team.jfs.app.oauth.OAuthHelper.updateAuthResponse(OAuthHelper.java:1436)
at com.ibm.team.jfs.app.oauth.OAuthHelper.updateResponseForAuthentication(OAuthHelper.java:1247)
3. 2013-08-27 18:58:17,849 [ http-bio-9443-exec-38] ERROR ronting.server.services.configure.ConfigureService - Server Error: Entry [e6f9a5002f631158]
java.lang.IllegalArgumentException: OAuthConsumerProperties must not be null
at com.ibm.team.jfs.app.oauth.OAuthHelper.validateConsumer(OAuthHelper.java:2302)
at com.ibm.team.jfs.app.oauth.OAuthHelper.getRequestTokenFromProvider(OAuthHelper.java:1010)
at com.ibm.team.jfs.app.oauth.OAuthHelper.updateAuthResponse(OAuthHelper.java:1436)
at com.ibm.team.jfs.app.oauth.OAuthHelper.updateResponseForAuthentication(OAuthHelper.java:1247)
--------------------------------------------------------------------------------------------------
The 2nd and 3rd errors differ with "er.services.servicedocument.ProjectResourceService" and "ronting.server.services.configure.ConfigureService" error root.
Also the weird thing for me is RM initialization:
2013-08-27 14:47:58,421 [ Start Level Event Dispatcher] INFO nternal.app.servlet.util.ServletDispatchingHandler - CRJZS0315I Servlet Dispatching Enabled
2013-08-27 14:47:58,421 [ Start Level Event Dispatcher] INFO nternal.app.servlet.util.ServletDispatchingHandler - CRJZS0318I Servlet Loopback Disabled
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9754I The application context properties are listed in subsequent messages.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9755I - The application context name is rm.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9756I - The application configuration directory is /home/IBM/JazzTeamServer/server/conf.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9757I - The application context configuration directory is /home/IBM/JazzTeamServer/server/conf/rm.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9758I - The application data directory is /home/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/rm/proxytemp/hc_118556433.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9759I - The application bundle data directory is /home/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/rm/eclipse/configuration/org.eclipse.osgi/bundles/117/data.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9760I - The application search path sequence is shown by order of precedence:
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9761I - The application search path detail is 1 : /home/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/rm/proxytemp/hc_118556433.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9761I - The application search path detail is 2 : /home/IBM/JazzTeamServer/server/tomcat/work/Catalina/localhost/rm/eclipse/configuration/org.eclipse.osgi/bundles/117/data.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9761I - The application search path detail is 3 : /home/IBM/JazzTeamServer/server/conf/rm.
2013-08-27 14:47:58,670 [ Start Level Event Dispatcher] INFO bm.rdm.fronting.server.bootstrap.RRSAppInitializer - CRRRS9761I - The application search path detail is 4 : /home/IBM/JazzTeamServer/server/conf.
2013-08-27 14:47:58,722 [Component Resolve Thread (Bundle 149)] INFO nternal.OverridablePropertyFileServerConfiguration -
To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum.
To find more information about a message, see the CLM Messages Information Center at
https://jazz.net/help-dev/CLMErrorMessages/index.jsp.
2013-08-27 14:47:58,722 [Component Resolve Thread (Bundle 149)] INFO nternal.OverridablePropertyFileServerConfiguration - CRJAZ1363I Loading the configuration from "file:/home/IBM/JazzTeamServer/server/conf/rm/fronting.properties".
2013-08-27 14:47:58,737 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9302I IConfig loading.
2013-08-27 14:47:58,738 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9310I Initializing (bootstrap) configuration.
2013-08-27 14:47:58,738 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9330I The Requirements Management server is loading this properties configuration file: fronting.properties.
2013-08-27 14:47:58,782 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.common.views.ViewNs - CRRRS4100I Initialise(https://localhost:9443/rdm)
2013-08-27 14:47:58,783 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9312I The Requirements Management application is using Jazz Team Server at root context URL https://localhost:9443/jts.
2013-08-27 14:47:58,783 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9318I The Requirements Management (RM) application is using the RM server at root context URL https://localhost:9443/rdm.
2013-08-27 14:47:58,791 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9313I The Requirements Management server is completing the initial load of this friends configuration file: friendsconfig.rdf.
2013-08-27 14:47:58,897 [Component Resolve Thread (Bundle 149)] WARN fronting.server.util.OAuthConsumerPropertiesLoader - CRRRS9768E No friends were found in this friends configuration file: https://localhost:9443/jts.
2013-08-27 14:47:59,333 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.bootstrap.Initializer - CRRRS9308I Server version 4.0.3 (I20130515_2124) startup complete.
2013-08-27 14:47:59,333 [Component Resolve Thread (Bundle 149)] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9938I Repository state is: INITIALIZING
2013-08-27 14:47:59,334 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.bootstrap.ClusterID - CRRRS9390I Cluster currently contains 0 members
2013-08-27 14:47:59,334 [Component Resolve Thread (Bundle 149)] INFO com.ibm.rdm.fronting.server.bootstrap.ClusterID - CRRRS9395I This node's ID is <jazz-lsbt>
2013-08-27 14:49:30,863 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9315I Initializing JPIMappingService...
2013-08-27 14:49:32,612 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9317I JPIMappingService(https://localhost:9443/jts/rootservices) was initialized successfully. Reloading fronting properties...
2013-08-27 14:49:32,613 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9330I The Requirements Management server is loading this properties configuration file: fronting.properties.
2013-08-27 14:49:32,614 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9322I The Jazz Team Server root context URL was reloaded from original value https://localhost:9443/jts and set to new value https://localhost:9443/jts.
2013-08-27 14:49:32,614 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9321I The Requirements Management server root context URL was reloaded from original value https://localhost:9443/rdm and set to new value https://localhost:9443/rdm.
2013-08-27 14:49:32,614 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9314I The Requirements Management server is loading this friends configuration file: friendsconfig.rdf.
2013-08-27 14:49:32,614 [ http-bio-9443-exec-11] WARN fronting.server.util.OAuthConsumerPropertiesLoader - CRRRS9768E No friends were found in this friends configuration file: https://localhost:9443/jts.
2013-08-27 14:49:32,637 [ http-bio-9443-exec-11] INFO com.ibm.rdm.fronting.server.common.views.ViewNs - CRRRS4100I Initialise(https://localhost:9443/rdm)
2013-08-27 14:49:58,855 [ http-bio-9443-exec-12] WARN ver.core.oauth.internal.OauthAuthenticationService - CRRRS01903E An authorization exception occurred while the principal was being retrieved.
java.lang.NullPointerException
So it breaks down on init stage, and also uses https://localhost:9443/rdm as a path, instead of <myhostname> and /rm. Maybe this is ok, I'm not sure.
Some other notes:
this is not a clean install, I'm "upgrading" from JTS 3.0.1, but using the non-standard way. I have a DB2 server on other machine and JTS 3.0.1 on another one. Also the openLdap is installed on third server. I decided to upgrade to 4.0.3 version and at that time my JTS machine hard drive crashed (machines can read my mind, huh?). So I have working DB2 Enterprise Edition with all Jazz databases and LDAP, but no previous RTC version available. I decided to try to install new RTC on new server and connect it to old databases - that's the only thing I can do to keep the data, right? I upgraded databases with new repotools, installed new RTC, passed all the setup successfully - and this RM error stopped me.
Hope, you could help me with that.
P.S. I'm using openSUSE Linux x64, DB2 9.7 Enterprise Edition x64, Tomcat 7.0 bundled into RTC 4.0.3 and openLdap. I know that there is a reccomendation to not to use openSUSE and use SLES, but my previous RTC installation works fine for a several years in the same case.
Any help appreciated.
Comments
Indradri Basu
May 31 '13, 3:07 a.m.Wondering if you have used any proxy server in your deployment ?