Attempting to upgrade Tomcat results into Rational Team Concert is no longer accessible through Eclipse client
After an upgrade of Tomcat server, the web client works, but attempting to access the RTC through Eclipse client or the scm command line tools results in this error:
An internal error occurred during: "Logging into rtctest.502.demo.com". java.lang.IllegalStateException: The URI "/ccm/authenticated/identity?
redirectPath=%2Fccm%2Fjauth-issue-token" is expected to be absolute
Reverting to the old tomcat works, but you require the new Tomcat in order to fix vulnerabilities.
An internal error occurred during: "Logging into rtctest.502.demo.com". java.lang.IllegalStateException: The URI "/ccm/authenticated/identity?
redirectPath=%2Fccm%2Fjauth-issue-token" is expected to be absolute
Reverting to the old tomcat works, but you require the new Tomcat in order to fix vulnerabilities.
Accepted answer
1. Go to Tomcat version which was upgraded
2. Find context.xml under upgraded Tomcat server (example, C:\Program Files\IBM\JazzTeamServer_5.0.2\server\tomcat\conf)
3. Back up the context.xml file
4. Change context.xml with the following setting (useRelativeRedirects="false" from true)
<!-- The contents of this file will be loaded for each web application -->
<Context useRelativeRedirects="false">
<!-- Default set of monitored resources -->
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<!-- Uncomment this to disable session persistence across Tomcat restarts -->
<!--
<Manager pathname="" />
-->
<!-- Uncomment this to enable Comet connection tacking (provides events
on session expiration as well as webapp lifecycle) -->
<!--
<Valve className="org.apache.catalina.valves.CometConnectionManagerValve" />
-->
</Context>
4. Save changes and restart the server.
5. Validate Eclipse and SCM clients should connect to RTC server without an error message.
2. Find context.xml under upgraded Tomcat server (example, C:\Program Files\IBM\JazzTeamServer_5.0.2\server\tomcat\conf)
3. Back up the context.xml file
4. Change context.xml with the following setting (useRelativeRedirects="false" from true)
<!-- The contents of this file will be loaded for each web application -->
<Context useRelativeRedirects="false">
<!-- Default set of monitored resources -->
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<!-- Uncomment this to disable session persistence across Tomcat restarts -->
<!--
<Manager pathname="" />
-->
<!-- Uncomment this to enable Comet connection tacking (provides events
on session expiration as well as webapp lifecycle) -->
<!--
<Valve className="org.apache.catalina.valves.CometConnectionManagerValve" />
-->
</Context>
4. Save changes and restart the server.
5. Validate Eclipse and SCM clients should connect to RTC server without an error message.
Comments
Thanks a lot! The first answer helped to solve this issue. In my case I used to install a new Tomcat version in 6.0.1. Then the RTC 5.0.2 Clients were not able to login anymore. Error below:
" An internal error occurred during: "Logging into <hotsname>".java.lang.IllegalStateException: The URI "/ccm/secure/authenticated/identity?redirectPath=%2Fccm%2Fjauth-issue-token" is expected to be absolute."
1 vote
The solution is applicable if you are using your own Tomcat sever instead of out of the box Liberty server that is shipped with RTC 601.
There is no more Tomcat Application server is bundled in CLM package, starting from 6.0.1 version. In this case, you might be forced to use Tomcat instead of Liberty.