Errors after Upgrade to RTC 2.0
I have just upgraded from RTC ExpressC 1.01 to RTC Express C 2.0 on linux. I did the database upgrade and was able to log into the server and view everything. I also upgraded my client (I am using RSA) to version 2.0. As soon as I try to connect, it completely hoses the server. I can get into the tomcat management console, but the Jazz interface never comes up. In fact I no longer see 'jazz' in the process stack with 'ps -ef | grep jazz'. When I try to connect with the web ui or the client UI, it eventual times out and gives me a tomcat error as follows:
javax.servlet.ServletException: Failed to determine authentication method com.ibm.team.repository.service.internal.identity.UserIdentityHelper.getAuthMethod(UserIdentityHelper.java:243) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1426) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) root cause org.apache.http.conn.HttpHostConnectException: Connection to https://hq.strongbackconsulting.com:9443 refused In my jazz.log file I find the following: 2009-07-09 11:14:11,939 WARN m.team.repository.service.internal.LogFeedAppender - CRJAZ0991I Failed to get the asynchronous scheduler service to schedule the log appender. Some log entries might be persisted to disk, but not appended to the log feed. 2009-07-09 11:14:11,939 ERROR ax.internal.ajaxapplication.AjaxApplicationServlet - Global Property Handler is unavailable 2009-07-09 11:14:11,939 WARN m.team.repository.service.internal.LogFeedAppender - CRJAZ0991I Failed to get the asynchronous scheduler service to schedule the log appender. Some log entries might be persisted to disk, but not appended to the log feed. 2009-07-09 11:14:11,939 ERROR ax.internal.ajaxapplication.AjaxApplicationServlet - Global Property Handler is unavailable 2009-07-09 11:14:11,940 WARN m.team.repository.service.internal.LogFeedAppender - CRJAZ0991I Failed to get the asynchronous scheduler service to schedule the log appender. Some log entries might be persisted to disk, but not appended to the log feed. 2009-07-09 11:14:11,940 ERROR ax.internal.ajaxapplication.AjaxApplicationServlet - Global Property Handler is unavailable 2009-07-09 11:14:11,941 WARN m.team.repository.service.internal.LogFeedAppender - CRJAZ0991I Failed to get the asynchronous scheduler service to schedule the log appender. Some log entries might be persisted to disk, but not appended to the log feed. 2009-07-09 11:29:38,877 INFO uration.OverridablePropertyFileServerConfiguration - CRJAZ1363I Loading configuration from "file:///opt/IBM/RTC/server/conf/jazz/teamserver.properties". 2009-07-09 11:29:39,654 INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1365I Attempting Initial Database Connection Using Db Name/Location: repositoryDB 2009-07-09 11:29:40,348 INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1364I Initial database connection successful Db Product Name: Apache Derby Db Product Version: 10.3.3.1 - (677131) Db URL: jdbc:derby:repositoryDB Jdbc Driver Name: Apache Derby Embedded JDBC Driver Jdbc Driver Version: 10.3.3.1 - (677131) 2009-07-09 11:29:40,516 INFO m.team.fulltext.service.internal.index.IndexConfig - CRJAZ8192E: Fulltext Index Location: workitemindex/fulltext_index/ 2009-07-09 11:29:43,031 WARN com.ibm.team.repository.servlet.TeamServerServlet - CRJAZ1181I Security notice during initialization: Allowing ADMIN user access. It is recommended that you disable the ADMIN user and create a real user with administrative rights. I also looked in the catalina.out log under the Tomcat directory and see this error: 11:26:09,943 WARN com.ibm.team.repository.web.internal.Activator - Error retrieving contextRoot java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.team.repository.web.internal.Activator.invokeCallbackMethod(Activator.java:277) at com.ibm.team.repository.web.internal.Activator.internalGetContextPathFromServeltCallback(Activator.java:263) at com.ibm.team.repository.web.internal.Activator.getContextPathFromServletCallback(Activator.java:257) at com.ibm.team.repository.web.internal.Activator.access$1(Activator.java:255) at com.ibm.team.repository.web.internal.Activator$1.run(Activator.java:205) at java.lang.Thread.run(Thread.java:810) Caused by: java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:906) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1203) at java.util.concurrent.Semaphore.acquire(Semaphore.java:287) at com.ibm.team.repository.server.servletbridge.ContextNameCallback.getContextPath(ContextNameCallback.java:30) ... 10 more Now, the ADMIN user message I understand. My RTC 2.0 instance is in a separate directory than my RTC 1.01 instance, and 1.01 starts and runs fine still. I've performed the new RTC2.0 install twice (with derby migration), and have received the same results. Anyone have any ideas? |
3 answers
I figured out my problem.
I installed the RTC 2.0 by copying the entire jazz directory to /opt/IBM/RTC/, meaing that the server.startup script was running from /opt/IBM/RTC/server. This will NOT work. I needs to be under a 'jazz' directory no matter what parent directory. Once I did that I re-ran the upgrade and everything is peachy keen. Mischief managed. |
I have just upgraded from RTC ExpressC 1.01 to RTC Express C 2.0 on linux. I did the database upgrade and was able to log into the server and view everything. I also upgraded my client (I am using RSA) to version 2.0. As soon as I try to connect, it completely hoses the server. I can get into the tomcat management console, but the Jazz interface never comes up. In fact I no longer see 'jazz' in the process stack with 'ps -ef | grep jazz'. When I try to connect with the web ui or the client UI, it eventual times out and gives me a tomcat error as follows: Hi Kenny When you did all the upgrades - did you export the old database into a tar file and then import it to the new database? And to be clear - are you able to use the web interface to see the server and its contents. anthony anthony |
Yes, I did the export from the 1.0 reposistoryDB using the repotools script to a tar file. I then imported the configuration in using the export option. Here is what I did and the order I did them:
copied the repositoryDB and workitemindex to a backup directory copied the repositoryDB and workitemindex to my new directory copied over the teamserver.properties file coped the tomcat-users.xml file over ran the repotools.sh -export toFile=export.tar from the 1.0 directory ran the repotools.sh -import fromFile=export.tar from the 2.0 directory Once the import was successful, I Launched the server.startup script. I just did this from scratch and now I can't get the web ui to work at all. Ideas? What am I missing here? |
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.