If you log in with your developerWorks ID, you can leave comments and feedback for the development team.

Problem

The ObjectGridManager.getObjectGrid method might generate an "ObjectGridRuntimeException: ObjectGrid <objectGridName> not found." exception in Java SE 6 provided in the IBM Software Development Kit in a dynamic deployment topology environment.
The first failure data capture (FFDC) log for the catalog service process might log a PersistenceException exception that is caused by a java.lang.ArrayIndexOutOfBoundsException exception when the ObjectGrid container tries to register itself with catalog server. An example of an FFDC log follows:

Exception = com.ibm.websphere.objectgrid.em.PersistenceException
Source = com.ibm.ws.objectgrid.catalog.placement.PlacementServiceImpl.joinPlacementGroup
probeid = 262
Stack Dump = com.ibm.websphere.objectgrid.em.PersistenceException
    at com.ibm.ws.objectgrid.em.EntityManagerImpl.findInternal(EntityManagerImpl.java:614)
    at com.ibm.ws.objectgrid.em.EntityManagerImpl.findForUpdate(EntityManagerImpl.java:492)
    at com.ibm.ws.objectgrid.catalog.placement.PlacementServiceImpl.createGrid(PlacementServiceImpl.java:1424)
    ...
Caused by: java.lang.ArrayIndexOutOfBoundsException
    at java.util.ArrayList.growAtEnd(Unknown Source)
    at java.util.ArrayList.add(Unknown Source)
    at com.ibm.ws.projector.collection.ManagedList.setKeys(ManagedList.java:128)
    ...

Cause

The ObjectGrid code that manages one-to-many and many-to-many relationships between entities incorrectly depends on implementation-specific behaviors in the java.util.ArrayList class. When the ArrayList class was updated in Java SE 6 for the IBM Software Development Kit, the entity relationship management code did not run properly. This code problem caused the placement service within the catalog server to fail to run properly.

Solution

Apply ObjectGrid cumulative intermediate fix 3.

Wiki Disclaimer and License

© Copyright IBM Corporation 2007,2010. All Rights Reserved.