Server Rename Generate Mappings fails with error CRJAZ1247E, Invalid URL for BuildEngine
Step 1 of Server Rename process to generate Mappings
repotools-jts -generateURLMappings additionalURLFile=additionalurl.txt adminPassword=*************** adminUserId=test_user repositoryURL=https://testserver:9443/jts toFile=mappings.txt
Fails with following Error:
CRJAZ1247E The request to the server failed. The server returned the HTTP error 500 with this error text: Internal Server Error.
JTS Logs hints at Build Engine having Invalid URLs
java.lang.RuntimeException: An error response was received from the Jazz Team Server. Status=500. Message: CRJZS0429E The server rename URL provider code detected an invalid URL. URL is buildforge://XX.XX.XX.XX:3966. URL category is AFFECTED. URL description is Build engine(s) with id(s): TestProject_Engine1
When we load the following URL, it is filled with errors:
https://testserver:9443/jts/urlMappingInformation
Snippet of Error on page
{"errorClass":"java.lang.RuntimeException","errorCode":500,"errorTraceMarshall":[{"errorTraceFileName":"URLPrefixSet.java","errorTraceClassName":"com.ibm.team.jfs.app.util.renameurlprovider.URLPrefixSet","errorTraceMethodName":"isValidUrl","errorTraceLineNumber":115}
Adding system property to Ignore Invalid URLs does not help as well
|
One answer
|
If the Build Engine host is not reachable from the JTS server, the mappings cannot be generated. The "/jts/urlMappingInformation" URL will fail to load and will display Errors
To verify:
Open RTC Eclipse Client and do a Test Connection on the Build Engine reported in the JTS logs.
To fix this
1. Fix the Build Engines, make sure Test Connection Works OR
2. Delete the Build Engines that are detected with Invalid URLs in the Log, additionally delete all the build jobs/history and build definitions associated with the build engines
Once you have fixed/deleted the Build Engines try loading the URL https://testserver:9443/jts/urlMappingInformation.
If it loads fine with the URLs for each application, then the mapping would also be generated.
------------------------------------------------------------------------------------------------------------------------- While you can still fix the Build Engines and any other Invalid URLs that are reported in the logs, in some case you might want to ignore them and continue with the same. Following URL for the Error reported. http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m2/index.jsp?topic=%2Fcom.ibm.messages.jazz.foundation%2FCRJZS0429E.html We tested the Property to ignore Invalid URLs and it seems to work fine. this will ignore other URLs as well, DOORS - RQMI integration URLs for example Steps:
On Tomcat add following line to server.startup (If it is distributed setup, add on all Tomcat servers)
Linux:
JAVA_OPTS="$JAVA_OPTS -Dcom.ibm.team.jfs.app.util.renameurlprovider.allowInvalidUrls=true"
export JAVA_OPTS
Windows:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.ibm.team.jfs.app.util.renameurlprovider.allowInvalidUrls=true
On WebSphere Application Server (WAS):
Add the following property to all profiles, JTS, RTC, RQM and RRC under:
Servers -> Server Types -> WebSphere Application Servers -> server1 -> Process definition -> Java Virtual Machine -> Custom properties
Name: com.ibm.team.jfs.app.util.renameurlprovider.allowInvalidUrls
Value: true
|
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.