It's all about the answers!

Ask a question

How to make Absolute path during rmUpdateProjectBackLinksOnline?

David Sakoda (2116) | asked May 26 '16, 7:38 p.m.
 I am upgrading to 5.0.1 from 4.0.3

CCM, JTS, QM have upgraded successfully to 5.0.1

I am at the last part of RM and get this error when running the final rmUpdateProjectBackLinksOnline step:

CRJAZ1728E A Repository Tools error occurred

detailed from log:
016-05-26 19:29:19,164 Provisioning using "E:\JazzTeamServer5\server\conf\rm\provision_profiles".
2016-05-26 19:29:19,180 repotools-rm -rmUpdateProjectBackLinksOnline adminPassword=************* adminUserId=dsakoda repositoryURL=https://my-host:9443/rm
2016-05-26 19:29:19,180   Jazz Foundation - Core Libraries, Version 5.0.1 (RJF-I20140805-1241)
  Rational DOORS Next Generation, Version 5.0.1 (RMS5.0.1-I20140805_2017)

2016-05-26 19:29:19,819 
 To submit questions about issues, go to the forum at 
 To find more information about a message, see the online product documentation.
2016-05-26 19:29:19,835 CRJAZ1363I Loading the configuration from "bundleresource://227.fwk1576623609:1/".
2016-05-26 19:29:19,882 CRJAZ1778I This server is configured as an application.
2016-05-26 19:29:20,100 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
2016-05-26 19:29:20,787 Retrieving project areas.
2016-05-26 19:29:21,489 java.lang.IllegalStateException: The URI "/jts/authenticated/identity?redirectPath=%2Fjts%2Fjauth-issue-token" is expected to be absolute java.lang.IllegalStateException: The URI "/jts/authenticated/identity?redirectPath=%2Fjts%2Fjauth-issue-token" is expected to be absolute
at com.sun.proxy.$Proxy96.describe(Unknown Source)

my teamserver.properies value from rm folder:\://my-host\:9443/rm

I can hit the login page fine from the browser using:

One answer

permanent link
David Sakoda (2116) | answered May 27 '16, 1:35 p.m.
 ok, this was not rtc's fault.  It was Tomcat.  I took the 4.0.3 tomcat and moved it to 5.0.1 dir.  I replaced the new 5.0.1 wars in the original working tomcat 4.0.3.  It works now. I'll see about upgrading tomcat to 7.0.69 later.

Your answer

Register or to post your answer.