server rename - preparing the mapping file
Hi,
I'm trying to create the mapping file to be used for server rename. However, the command: repotools-jts.bat -generateURLMappings toFile=mappings.txt adminUserId=BVO adminPassword=<thepassword> additionalURLFile=additionalurl.txt repositoryURL=https://asist-srv:9449/jts results in this error: 2014-04-01 11:49:37,397 Repo Tools2014-04-01 11:49:37,398 java.version=1.6.02014-04-01 11:49:37,398 java.runtime.version=pwa6460sr15-20131017_01 (SR15)2014-04-01 11:49:37,401 Provisioning using "C:\IBM\JazzTeamServer4.0.6\server\conf\jts\provision_profiles".2014-04-01 11:49:37,416 repotools-jts -generateURLMappings additionalURLFile=additionalurl.txt adminPassword=******************* adminUserId=BVO repositoryURL=https://asist-srv:9449/jts toFile=mappings.txt2014-04-01 11:49:37,419 Jazz Foundation - Core Libraries, Version 4.0.6 (RJF-I20140130-1407)2014-04-01 11:49:38,685 2014-04-01 11:49:38,685 CRJAZ2233I The server at https://asist-srv:9449/jts/urlMappingInformation is being contacted to collect URL information.2014-04-01 11:49:38,729 CRJAZ1247E The request to the server failed. The server returned the HTTP error 500 with this error text: Internal Server Error.com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ1247E The request to the server failed. The server returned the HTTP error 500 with this error text: Internal Server Error. at com.ibm.team.repository.transport.client.ClientHttpUtil.throwHttpClientError(ClientHttpUtil.java:1444) at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:525) at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:322) at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:220) at com.ibm.team.repository.transport.client.ClientHttpUtil.executeHttpMethod(ClientHttpUtil.java:229) at com.ibm.team.repository.transport.client.RestClientConnectionBase.executeMethod(RestClientConnectionBase.java:318) at com.ibm.team.repository.transport.client.RestClientConnectionBase.doMethod(RestClientConnectionBase.java:181) at com.ibm.team.repository.transport.client.RestClientConnectionBase.doGet(RestClientConnectionBase.java:122) at com.ibm.team.repository.transport.client.TeamRawRestServiceClient$RawRestClientConnection.doGet(TeamRawRestServiceClient.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254) at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110) at com.ibm.team.repository.client.internal.RawRestServiceClientProxy$RestClientConnectionProxy.invoke(RawRestServiceClientProxy.java:121) at com.sun.proxy.$Proxy9.doGet(Unknown Source) at com.ibm.team.repotools.commands.remote.AbstractRenameMappingsCommand.doGetOnURL(AbstractRenameMappingsCommand.java:121) at com.ibm.team.repotools.commands.remote.AbstractRenameMappingsCommand.getUrlMappingInformationInputStream(AbstractRenameMappingsCommand.java:131) at com.ibm.team.repotools.commands.remote.internal.GenerateURLMappingsCommand.execute(GenerateURLMappingsCommand.java:105) at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:67) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:816) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:891) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408) at org.eclipse.equinox.launcher.Main.main(Main.java:1384)2014-04-01 11:49:38,732 CRJAZ1728E A Repository Tools error occurred. For more information, see this log file: C:\IBM\JazzTeamServer4.0.6\server\repotools-jts_generateURLMappings.log I have CLM406 installed. Any thoughts why I'm seeing this error? Regards, Bernd. |
3 answers
This is a http 500 server error, so you can have a look at the server log to see what's exactly going on.
The server logs are located in the following directories: Assuming you're using Tomcat: (JazzServer)/server/tomcat/logs In case of WAS: (WebSphere install dir)/AppServer/profiles/(profile name)/logs/(server name) |
The same error in server rename can be seen in some scenarios like:
1) the server itself does not run properly before rename attempt. this basically will have more clues in jts.log, ccm/qm/rm.log indicating what could be wrong. For example, communication between jts and qm may have problem and so on. 2) teamserver.properties file has some wrong configuration: this requires close examination and make sure everything is corrrect 3) some integration part such as BF integration not configured properly or working could lead to similar error. QM+Doors integration may also have impact etc, checking with jts/qm/ccm logs would have some info related to those if that is the case. In many cases, I believe this could require further investigation and contacting support is a good option. Just some thoughts to share with 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.
Comments
Hi Bernd,
Can you look into your ccm.log to check what error messages you have there at the same time?
Hi @krzysztofkazmierczyk,
I looked into ccm.log and found that an error is thrown while checking the URL of a build agent which seems to be referenced in an obsolete project area:
2014-04-01 13:44:46,405 [http-bio-9449-exec-33 @@ 13:44 BVO /jts/urlMappingInformation] ERROR com.ibm.team.repository - CRJZS0429E The server rename URL provider code detected an invalid URL. URL is buildagent://192.168.0.231:6666. URL category is AFFECTED. URL description is Build engine(s) with id(s): RDz probeerseltje engine, RDz-RTC Engine.
java.lang.RuntimeException: CRJZS0429E The server rename URL provider code detected an invalid URL. URL is buildagent://192.168.0.231:6666. URL category is AFFECTED. URL description is Build engine(s) with id(s): RDz probeerseltje engine, RDz-RTC Engine
This seems to cause the error. However, I'm only trying to export the mapping file and in the server's admin page everything seems to be ok.