PM88437: The CWOBJ1550W message and the NullPointerException exception occur when you start a catalog server.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

Closed as program error.

Error description

PrimaryShardI W CWOBJ1550W: The primary
(IBM_SYSTEM_work.status:work.status:0) shard received exceptions
while replicating from the primary shard on the
catalog_cluster:catalog1_C-0 primary container.
The primary shard continues to poll the primary shard. Exception
received:
com.ibm.websphere.objectgrid.ObjectGridRuntimeException:
java.lang.NullPointerException
at
com.ibm.ws.objectgrid.ObjectGridImpl.applyRevisionProto(ObjectGr
idImpl.java:5656)
at
com.ibm.ws.objectgrid.replication.PrimaryShardImpl$RevisionQuery
Handler.runXIOAPQueryRevision(PrimaryShardImpl.java:3884)
at
com.ibm.ws.objectgrid.replication.PrimaryShardImpl$RevisionQuery
Handler.run(PrimaryShardImpl.java:3651)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
utor.java:1156)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
cutor.java:626)
at
com.ibm.ws.objectgrid.thread.XSThreadPool$Worker.run(XSThreadPoo
l.java:280)
Caused by: java.lang.NullPointerException
at
com.ibm.ws.objectgrid.map.BaseMap.applyKeys(BaseMap.java:10864)
at
com.ibm.ws.objectgrid.map.BaseMap.applyRevisionTxProto(BaseMap.j
ava:10237)
at
com.ibm.ws.objectgrid.ObjectGridImpl.applyRevisionProto(ObjectGr
idImpl.java:5587)
... 5 more

Local fix

Problem summary

****************************************************************
* USERS AFFECTED: Users of WebSphere eXtreme Scale who have *
* eXtremeMemory (XM) enabled on the catalog *
* server. *
****************************************************************
* PROBLEM DESCRIPTION: The NullPointerException exception *
* occurs on the catalog server when *
* eXtremeMemory is enabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A problem existed where there was a mismatch on whether
eXtremeMemory was enabled for a map. The mismatch was
corrected so that the code correctly determines whether
eXtremeMemory was enabled for a map.