Issue while server rename
Hi,
We have distributed production environment with CLM 6.0.2 and we are in process of creating a staging server.
We are using standalone machine for staging where we have restored the production database, installed CLM 6.0.2 and copied replaced conf folder in staging of production server.
Updated teamserver.properties file. Both production and staging are in isolated network.
We are getting below error after starting the application on staging.
The server status cannot be retrieved.ID CRJAZ1505E
hide details
The "com.ibm.team.repository.service.internal.ServerStatusRestService" service failed to activate because a service that it depends on, "com.ibm.team.repository.service.IServerDescriptionService", failed to be activated.ID CRJAZ1972E
com.ibm.team.repository.common.transport.TeamServiceRegistryException
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:384)
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:753) com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133) com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:292) com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:301) com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getServiceForRemoteAccess(OsgiServicesManager.java:696) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2433) com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2315) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1794) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:138) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456) com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125) com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92) com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165) com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198) com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926) com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023) com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3703) com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962) com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311) com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87) com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784) com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)
Caused by:
The "com.ibm.team.repository.service.internal.ServerDescriptionService" service failed to activate because a service that it depends on, "com.ibm.team.repository.service.IBaseServerDescriptionService", failed to be activated. (com.ibm.team.repository.common.transport.TeamServiceRegistryException)ID CRJAZ1972E
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:384)
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:753) com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getService(ServiceProviderActivationManagerOwner.java:133) com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:292) ... 49 more.
Caused by:
The service "com.ibm.team.repository.service.internal.BaseServerDescriptionService" has some invalid configuration properties. CRJAZ1125I The configuration property value "https://testserverhostname:9443/jts" is not valid for the property "server.webapp.url". CRJAZ2197E The public URI for this server has already been set to "https://productionserverhostname/jts". It cannot be changed to "https://testserverhostname:9443/jts" once the server has been configured. If the server has moved to a new location at "https://testserverhostname:9443/jts", follow the instructions to rename the server. (com.ibm.team.repository.common.transport.TeamServiceRegistryException)ID CRJAZ1126I
com.ibm.team.repository.common.transport.internal.registry.ServiceConfiguration.assertValidProperties(ServiceConfiguration.java:292)
com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.bindConfigurationProperties(AbstractActivationManagerOwner.java:268) com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.performActivation(AbstractActivationManagerOwner.java:703) com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:766) ... 56 more
Do I need to perform server rename ?
If so where I should generate mapping file on staging or in production ?
Regards,
Arun
|
One answer
Hi Arun,
yes, you need to perform a proper server rename. This part of your error message is a clear hint:
""https://testserverhostname:9443/jts" is not valid for the property "server.webapp.url". CRJAZ2197E The public URI for this server has already been set to "https://productionserverhostname/jts". It cannot be changed to "https://testserverhostname:9443/jts" once the server has been configured. If the server has moved to a new location at "https://testserverhostname:9443/jts",follow the instructions to rename the server. "
Here is a link as an entry to the topic, showing workflow and linking to e.g. the mapping file creation:
Server rename is not trivial. You will have to read through all of the information and follow it meticulously. I suggest keeping snapshots of your staging environment VMWares in case you need to redo. Once you are comfortable with the procedure in case you need to repeat it in the future I suggest scripting vital parts.
If this answers your question please mark this answer as accepted. - Arne |
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.