Problems to configure RTC 3.0.1 Beta 3 and RC (register LPA)
Hello,
I have problems to use the latest build of RTC (Beta and RC). The installation was made sucessfully, but when I try to execute the initial setup wizard, I got the messages below in the catalina.out: 08:47:23,166 WARN com.ibm.team.lpa.LPAInitializer - Error determining LPA build ID java.lang.Exception: Failed to open version file /WEB-INF/built-on.txt at com.ibm.team.lpa.LPAInitializer.init(LPAInitializer.java:69) at com.ibm.team.jfs.app.servlet.AppContainerServlet.executeAppInitializers(AppContainerServlet.java:423) at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:245) 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 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) 08:47:23,309 INFO com.ibm.team.jfs.app.ConfigUtil - CRJZS0158I Loading configuration file "admin.properties" from the path "/opt/IBM/JazzTeamServer/server/conf/admin" for the application context "admin". 08:47:23,309 INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsTargetHost=default 08:47:23,309 INFO com.ibm.team.lpa.config - com.ibm.team.lpa.app.jtsVirtualHost=default 08:47:23,312 INFO com.ibm.team.lpa.config - CRJCA0028I Initialization of the Lifecycle Project Administration Application failed. Please register the Lifecycle Project Administration application with the Jazz Team Server. I suspect that I should fill some information in the admin.properties, but I am not sure. Are the RM, CCM, QM and LPA supposed to run in a single computer? The are modifications to be made in the configuration files before start the server, or run the setup wizard? What is really odd is that the same error is thrown from windows and linux boxes. In the registry application step of the wizard, Lifeclyle Project Administration is grayed out and after execution of wizard I understand tha LPA application was successfully registered (as showed in the wizard). The log, however show that something goes wrong: 08:47:23,312 INFO com.ibm.team.lpa.config - CRJCA0028I Initialization of the Lifecycle Project Administration Application failed. Please register the Lifecycle Project Administration application with the Jazz Team Server. java.lang.IllegalArgumentException: OAuthConsumerProperties must not be null at com.ibm.team.jfs.app.oauth.OAuthHelper.validateConsumer(OAuthHelper.java:1533) at com.ibm.team.jfs.app.oauth.OAuthHelper.getAuthorizationHeaderInternal(OAuthHelper.java:1433) at com.ibm.team.jfs.app.oauth.OAuthHelper.addAuthorizationHeader(OAuthHelper.java:1087) at com.ibm.rdm.fronting.server.core.oauth.internal.OauthAuthenticationService.authenticateRequest(OauthAuthenticationService.java:237) at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.sendHttpRequest(HttpClientWrapperService.java:591) at com.ibm.rdm.fronting.server.core.internal.HttpClientWrapperService.getResource(HttpClientWrapperService.java:127) at com.ibm.rdm.fronting.server.core.repository.RepositoryAccessManager.recalculateRepositoryState(RepositoryAccessManager.java:140) at com.ibm.rdm.fronting.server.core.repository.RepositoryAccessManager.initialize(RepositoryAccessManager.java:72) at com.ibm.rdm.fronting.server.bootstrap.RRSAppInitializer.init(RRSAppInitializer.java:93) at com.ibm.team.jfs.app.servlet.AppContainerServlet.executeAppInitializers(AppContainerServlet.java:423) at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:245) 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) After wizard execution, I am not able to create new projects using LPA application. The buttons to do that does not appear in the application. The project tab in the LPA application is empty. Could someone give me some directions to get the cause of this error? I am very excited to solve this problems and get in touch with this new release. Thanks in advance! |
6 answers
Not sure if this is the same problem, but this work item was raised on RC1
https://jazz.net/jazz/web/projects/Jazz%20Collaborative%20ALM#action=com.ibm.team.workitem.viewWorkItem&id=161292 |
|
Yep, the same problem. I will track this wi.
Thanks Not sure if this is the same problem, but this work item was raised on RC1 |
The LPA error that you're seeing shouldn't cause any problems with the functionality of the applications. The only thing that doesn't work properly because of this error is the logging of the LPA build id in the admin.log. If you're having other problems with your setup, I don't think this would be the root cause. Are you having trouble completing the setup? If so, are there any other errors in the logs?
Matt Jarvis LPA Development Lead |
|
I'm sorry, I just realized that I missed the second stack trace in the first message. That error could indicate a problem, but there is a bug that causes it to be logged prematurely sometimes. (See http://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=157866)
Are you able to successfully complete the LPA setup wizard at https://<server>:<port>/admin/setup? If so, then you should be registered with the JTS correctly. If you're using Firefox 4, the blank page you're seeing could be another problem that was fixed since Beta 3. (See http://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=158841) If that is your problem, Firefox 3.6 or IE 8 should work. |
Hello,
We are trying to setup RTC 3.0.1 rc 1. Our setup is on a Windows 2008 server, with DB2 9.7 and WebSphere 7.0.0.13. During the setup we are unable to register the Requirement Management application. We are getting the following error: @ID@E An error occurred while attempting to access the Discovery URL for the application. Please ensure that the application has been installed and provisioned correctly. hide details Unable to load https://dshsapoly4199rt.dshs.wa.lcl:9443/rm/scr?dojo.preventCache=1302897215261 status:500 Does anyone have any ideas what went wrong or how to fix this? |
Hello, Hi Joyce Try running setup again and see if that helps. If that does not help - this might relate back to a mistake during the install. Do you remember if you ran Installation Manager using the "Run As Administrator" command, and avoided the "virtual" directory - c:\program files(x86)\... as the install location. If not, try uninstalling, removing all the directories and files left after the install, and install again. I would also wait a while and see if anyone has any better explanation and a less drastic suggestions as a re-install. anthony |
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.