RRC 4.0 to 4.0.2 Upgrade - ArrayIndexOutOfBoundsException
Hi
While upgrading CLM 4.0 to 4.0.2 , RRC online upgrade fails ( Can not initiate online upgrade ) . In the rm.log I could find below error.
Kindly suggest
2013-06-10 22:58:59,804 [Component Resolve Thread (Bundle 76)] INFO nternal.OverridablePropertyFileServerConfiguration - CRJAZ1363I Loading the configuration from "file:/D:/IBM/JazzTeamServer402/server/conf/rm/fronting.properties".
2013-06-10 22:59:00,085 [Component Resolve Thread (Bundle 76)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9310I Initializing (bootstrap) configuration
2013-06-10 22:59:00,085 [Component Resolve Thread (Bundle 76)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9320I Loading fronting.properties
2013-06-10 22:59:00,117 [Component Resolve Thread (Bundle 76)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9312I Using JTS at: http://<server>:9080/jts
2013-06-10 22:59:00,117 [Component Resolve Thread (Bundle 76)] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9313I Loading friendsconfig.rdf
2013-06-10 22:59:00,680 [Component Resolve Thread (Bundle 76)] INFO fronting.server.util.OAuthConsumerPropertiesLoader - CRRRS9752I Loaded friends configuration from D:\IBM\JazzTeamServer402\server\conf\rm\friendsconfig.rdf.
2013-06-10 22:59:00,789 [Component Resolve Thread (Bundle 76)] INFO com.ibm.rdm.fronting.server.bootstrap.Initializer - CRRRS9308I Server version 4.0.2 (I20130222_1706) startup complete
2013-06-10 22:59:00,789 [Component Resolve Thread (Bundle 76)] INFO ing.server.core.repository.RepositoryAccessManager - CRRRS9938I Repository state is: INITIALIZING
2013-06-10 23:08:08,349 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9315I Initializing JPIMappingService
2013-06-10 23:08:08,755 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9317I JPIMappingService initialized successfully using: http://<server>:9080/jts/rootservices
2013-06-10 23:08:08,755 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9318I Reloading properties due to potential changes by JPIMappingService
2013-06-10 23:08:08,755 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9320I Loading fronting.properties
2013-06-10 23:08:08,755 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9312I Using JTS at: http://<server>:9080/jts
2013-06-10 23:08:08,755 [ WebContainer : 4] INFO com.ibm.rdm.fronting.server.util.ConfigImpl - CRRRS9313I Loading friendsconfig.rdf
2013-06-10 23:12:37,581 [ WebContainer : 11] ERROR ronting.server.services.adminhome.AdminHomeService - Server Error: Entry [907d856ad6f0febf]
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1
at com.ibm.rdm.fronting.server.util.IConfig$ReleaseInfo.fromBuiltOn(IConfig.java:100)
at com.ibm.rdm.fronting.server.util.ConfigImpl.getRequiredReleaseInfo(ConfigImpl.java:1216)
at com.ibm.rdm.fronting.server.core.repository.RepositoryAccessManager.recalculateRepositoryState(RepositoryAccessManager.java:278)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.checkRepositoryState(RRSRestServiceBase.java:797)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:186)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:148)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:155)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613)
Thank you
Accepted answer
We researched this error and there are previous times where a CLM 4.0.2 installation has failed during the setup wizard at the register rm application stage, with this same exception. The resolution appears to be to clear the WAS cache. Since you have removed the database and left WAS in place, WAS is about the only part of the old installation left.
Please try this:
1. uninstall the 4.0.2 applications from WAS
2. clear the WAS cache
3. install the 4.0.2 applications into WAS
Instructions on how to clear the WAS cache:
Shut down WAS
Rename the directories "temp" and "wstemp" under ...\WebSphere\AppServer\profiles\AppSrv01
Start up WAS again
* Note that I believe there is a command in WAS 7.0.0.23 to use command line to clear the cache too.
clearClassCache.sh|bat . It can be found in the was_root/bin directory.
Please try this:
1. uninstall the 4.0.2 applications from WAS
2. clear the WAS cache
3. install the 4.0.2 applications into WAS
Instructions on how to clear the WAS cache:
Shut down WAS
Rename the directories "temp" and "wstemp" under ...\WebSphere\AppServer\profiles\AppSrv01
Start up WAS again
* Note that I believe there is a command in WAS 7.0.0.23 to use command line to clear the cache too.
Comments
1 vote
One other answer
Hi Tom,
Are you certain that the server running in this case is really 4.0.2?
I checked the code referenced in your stack trace and the line numbers don't match at all. The call to fromBuiltOn() in ConfigImpl.getRequiredReleaseInfo should be on line 1533 when I look at the 4.0.2 code, yet your trace is showing it to be at line 1216. And line number 100 for fromBuiltOn() is also not possible.
I had a look at the 4.0 code and there those line numbers do in fact align perfectly. So it would seem that you are actually running the 4.0 server during the online phase, and not 4.0.2.
Are you certain that the server running in this case is really 4.0.2?
I checked the code referenced in your stack trace and the line numbers don't match at all. The call to fromBuiltOn() in ConfigImpl.getRequiredReleaseInfo should be on line 1533 when I look at the 4.0.2 code, yet your trace is showing it to be at line 1216. And line number 100 for fromBuiltOn() is also not possible.
I had a look at the 4.0 code and there those line numbers do in fact align perfectly. So it would seem that you are actually running the 4.0 server during the online phase, and not 4.0.2.
Comments
showing 5 of 11
show 6 more comments
Comments
Bo Chulindra
JAZZ DEVELOPER Jun 11 '13, 3:32 p.m.Stef van Dijk
FORUM MODERATOR / JAZZ DEVELOPER Jun 11 '13, 4:01 p.m.