It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×7,386
×5,999
×3,952
×267
×2

question asked: Jun 11 '13, 1:28 a.m.
question was seen: 6,134 times
last updated: Jun 14 '13, 9:28 a.m.

Related questions

FAQ - How this Forum works

RRC 4.0 to 4.0.2 Upgrade - ArrayIndexOutOfBoundsException

0
Thomman TJ (95●2●11●11) | asked Jun 11 '13, 1:28 a.m.
retagged Jun 11 '13, 9:24 a.m. by Michelle De Armas (261●2)
 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

Comments
Bo Chulindra commented Jun 11 '13, 3:32 p.m.
JAZZ DEVELOPER

This same problem was also run into in https://jazz.net/forum/questions/96363/clm401-install-error-rm-registration-fails-with-was80-64bitdb2-64bitwin-7-64bit. Unfortunately as of right now there's still no solution.

Stef van Dijk commented Jun 11 '13, 4:01 p.m. | edited Jun 11 '13, 4:01 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

Actually the problem in the other forum thread illustrates my point a bit.
When you look at the comment there made by Guido Schneider on May 24, you can see how the line numbers are quite different while he too is trying to upgrade to 4.0.2:
(IConfig.java:111 and ConfigImpl.java:1531 compared to Tom's case: IConfig.java:100 and ConfigImpl.java:1216).
So while the error is the same, it's clear that the level of code being executed by each is quite different.

Accepted answer

5
permanent link
Ian Wark (797●1●35●50) | answered Jun 13 '13, 2:45 a.m.
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.
Thomman TJ selected this answer as the correct answer
Comments
1
Thomman TJ commented Jun 13 '13, 6:23 a.m.

Thanks Ian ,  It helped met to resolve the issue.  


1. Uninstall the 4.0.2 applications from WAS.
2. Shut down WAS 
3. Clear the WAS cache 
* Run the command clearClassCache.sh|bat. It is in the was_root/bin directory.
* Rename or remove the directories "temp" and "wstemp" under ...\WebSphere\AppServer\profiles\AppSrv01 if they still exist.
4. Start up WAS again 
5. Reinstall the 4.0.2 applications into WAS.


    

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Stef van Dijk (2.0k●1●7●9) | answered Jun 11 '13, 9:49 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
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.
Comments
Bo Chulindra commented Jun 11 '13, 3:37 p.m.
JAZZ DEVELOPER

that's interesting because you can see this line in the log:

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".

So this would suggest that RM 4.0 was installed instead of RM 4.0.2?

@kochuthara: Can you open the file D:/IBM/JazzTeamServer402/server/conf/rm/build/built-on.txt and tell us the value in there?

Stef van Dijk commented Jun 11 '13, 3:50 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

It is perplexing. One possibility is that the FQDN is mapping back to the old server instead of the new one (since presumably as part of the upgrade it is still at the same url). You might try accessing the server Status Summary from both jts/admin and rm/rmadmin to verify they both indicate the server is at 4.0.2. I have seen cases of the 4.0.2 RM server referencing an older (ie, 4.0) JTS server because the host name was not mapped on the RM server to reference the new/upgraded server.

Thomman TJ commented Jun 12 '13, 2:55 p.m.

I have only one server, which I was trying to upgrade.  

                 Windows 2008 Server 64 bit
                 WAS 7.0.0.23 
                 CLM 4.0 
I was trying to upgrade to CLM 4.0.2

Thomman TJ commented Jun 12 '13, 3:12 p.m.
@Stef

When I started the server, after upgrade, WAS customer property JAZZ_HOME was referring old CLM 4.0 install location,  I think log was submitted at that time, Later I change JAZZ_HOME to 4.0.2 location, but issue remains same . java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1
Thomman TJ commented Jun 12 '13, 3:19 p.m. | edited Jun 12 '13, 4:48 p.m.


I discard the upgrade and re installed CLM 4.0.2 .  

to my surprise while registering applications, rm application did not registered and throw same error  ArrayIndexOutof Bound


An error occurred while attempting to register the applications.ID CRJAZ1726E
hide details
Request to service http://<server-fqdn>:9080/rm/configureRegistration failed with status code 400 and response body: CRRRS9639E The RM application registration handler could not save the configuration: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1
com.ibm.team.repository.common.TeamRepositoryException
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.checkHttpResponse(FriendsAdminRestService.java:820)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:468)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService$UpdatingFriendResponseHandler.handleResponse(ApplicationRegistrationFriendRestService.java:1)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:945)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:910)
com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.executeHttpRequest(FriendsAdminRestService.java:772)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.notifyAppRegistrationHandler(ApplicationRegistrationFriendRestService.java:361)
com.ibm.team.repository.service.internal.discovery.ApplicationRegistrationFriendRestService.postRegisterApp(ApplicationRegistrationFriendRestService.java:201)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:600)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
$Proxy1504.postRegisterApp(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:600)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:541)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2104)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1924)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1800)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
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:831)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
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:1613)


Bo Chulindra commented Jun 12 '13, 4:00 p.m.
JAZZ DEVELOPER

@kochuthara: try what Stef suggested and visit both jts/admin and rm/admin to see what versions they are.

Stef van Dijk commented Jun 12 '13, 5:04 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

@kochuthara: the error you are posting now, while also an ArrayIndexOutOfBoundsException, appears to be happening in a radically different place in the code. Maybe it's just bubbling up from the same location, but on the surface at least this is a very different error and down in the Foundation code.

To be honest, I think trying to chase this through forum posts will prove difficult and frustrating, so if possible I'd highly recommend opening a ticket with IBM Support to have this properly investigated. Here is the link: http://www-01.ibm.com/software/rational/support/contact.html.

Thomman TJ commented Jun 13 '13, 12:02 a.m.

I do have severity 1 defects, yet to get any solution 


@Bo Chulindra


/rm/build/build-on 

 4.0.2   (I20130222_1706)

jts/admin 
   Jazz Foundation - Core Libraries    4.0.2   RJF-I20130222-1204

Stef van Dijk commented Jun 13 '13, 10:53 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

@kochuthara: While I understand that Ian was able to resolve your problem, could you please direct me to your severity 1 defects? Are these PMRs or jazz.net work items?
I want to follow up on this and understand if these were actually being investigated, and if not, why not.

Thomman TJ commented Jun 13 '13, 9:04 p.m.

[PMR 49725,000,749] RRC: Migration fails on upgrade from 4.0 to 4.0.2 

Stef van Dijk commented Jun 14 '13, 9:28 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Thanks @kochuthara. I can see the escalation was created earlier this week and picked up by Ian and the support team and has been resolved/closed.

showing 5 of 11 show 6 more comments

Your answer

Register or to post 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.