Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Upon upgrade to WebSphere Application Server V7 from V6.1, the following error is reported in the SystemOut.log. . [6/30/11 10:59:25:682 AST] 0000001c SibMessage E [Bus] CWSIP0051E: The destination "Destination Name" cannot be recovered from the data store due to error com.ibm.websphere.sib.exception.SIResourceException: java.lang.NullPointerException at com.ibm.ws.sib.processor.impl.BaseDestinationHandler.reconstitut e(BaseDe stinationHandler.java:952) at com.ibm.ws.sib.processor.impl.DestinationManager.reconstitute(De stinatio nManager.java:724) at com.ibm.ws.sib.processor.impl.MessageProcessor.reconstitute(Mess ageProce ssor.java:2391) at com.ibm.ws.sib.processor.impl.MessageProcessor.startInternal(Mes sageProc essor.java:1549) at com.ibm.ws.sib.processor.impl.MessageProcessor.start(MessageProc essor.ja va:1342) at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagin gEngineI mpl.java:609) at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate( HAManage rMessagingEngineImpl.java:995) at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThr ead.java :92) Caused by: java.lang.NullPointerException at com.ibm.ws.sib.msgstore.persistence.objectManager.PersistableImp l.getTup leType(PersistableImpl.java:1027) at com.ibm.ws.sib.msgstore.persistence.objectManager.PersistentMess ageStore Impl.readNonStreamItems(PersistentMessageStoreImpl.java:975) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink._initializeIt ems(Item StreamLink.java:221) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink._items(ItemSt reamLink .java:267) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink.newNonLocking ItemCurs or(ItemStreamLink.java:774) at com.ibm.ws.sib.msgstore.ItemStream.newNonLockingItemCursor(ItemS tream.ja va:690) at com.ibm.ws.sib.processor.impl.store.itemstreams.PubSubMessageIte mStream. reconstitute(PubSubMessageItemStream.java:221) at com.ibm.ws.sib.processor.impl.destination.PubSubRealization.reco nstitute (PubSubRealization.java:467) at com.ibm.ws.sib.processor.impl.BaseDestinationHandler.reconstitut e(BaseDe stinationHandler.java:907) ... 7 more . [6/30/11 10:59:51:263 AST] 00000030 DefaultMessag I org.springframework.jms.listener.DefaultMessageListenerContainer handleListenerSetupFailure Setup of JMS message listener invoker failed for destination 'topic://myTopic?topicSpace="TopicSpaceName"&busName=Bu sName' - trying to recover. Cause: CWSIA0085E: An exception was received during the call to the method JmsMsgConsumerImpl.createCoreConsumer: com.ibm.ws.sib.processor.exceptions.SIMPDestinationCorruptExcept ion: CWSIK0027E: The destination with name "Destination Name" is corrupt. An FFDC is also generated reporting the following error: [6/30/11 10:59:24:334 AST] FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.ws.sib.processor.impl.BaseDestinationHandler.re constitu te ProbeId:1:940:1.700.3.38 Reporter:com.ibm.ws.sib.processor.impl.BaseDestinationHandler@45 ae90c9 java.lang.NullPointerException at com.ibm.ws.sib.msgstore.persistence.objectManager.PersistableImp l.getTup leType(PersistableImpl.java:1027) at com.ibm.ws.sib.msgstore.persistence.objectManager.PersistentMess ageStore Impl.readNonStreamItems(PersistentMessageStoreImpl.java:975) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink._initializeIt ems(Item StreamLink.java:221) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink._items(ItemSt reamLink .java:267) at com.ibm.ws.sib.msgstore.cache.links.ItemStreamLink.newNonLocking ItemCurs or(ItemStreamLink.java:774) at com.ibm.ws.sib.msgstore.ItemStream.newNonLockingItemCursor(ItemS tream.ja va:690) at com.ibm.ws.sib.processor.impl.store.itemstreams.PubSubMessageIte mStream. reconstitute(PubSubMessageItemStream.java:221) at com.ibm.ws.sib.processor.impl.destination.PubSubRealization.reco nstitute (PubSubRealization.java:467) at com.ibm.ws.sib.processor.impl.BaseDestinationHandler.reconstitut e(BaseDe stinationHandler.java:907) at com.ibm.ws.sib.processor.impl.DestinationManager.reconstitute(De stinatio nManager.java:724) at com.ibm.ws.sib.processor.impl.MessageProcessor.reconstitute(Mess ageProce ssor.java:2391) at com.ibm.ws.sib.processor.impl.MessageProcessor.startInternal(Mes sageProc essor.java:1549) at com.ibm.ws.sib.processor.impl.MessageProcessor.start(MessageProc essor.ja va:1342) at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagin gEngineI mpl.java:609) at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate( HAManage rMessagingEngineImpl.java:995) at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThr ead.java :92)
Local fix
No local fix is available but as a workaround, implement the Reset Destination Command to delete and recreate the corrupt destination. . http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp? topic=/c om.ibm.websphere.base.iseries.doc/info/iseries/ae/tjo_reset_dest .html
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: After migration of WAS from * * version 6.1 to higher version, * * NullPointerException would be * * observed which would eventually * * result in the destination being * * corrupt. * **************************************************************** * RECOMMENDATION: * **************************************************************** The NullPointerException that is reported is due to the difference in the way non-persistent messages are implemented in version 6.1 and in version 7 (v7.0 and v8.0). In WebSphere Application Server V6.1, non-persistent messages were added to a stream. During reconstitute while recreating the in-memory state, we iterate over the stream and there was a possibility of NULL being retrieved and so a check being made for the NULL occurrence. In WebSphere Application Server V7 (and V8), non-persistent messages were not added to a stream. Hence, during reconstitute while recreating the in-memory state, we don't iterate over the stream and hence there is no possibility of NULL occurrence. So, after migration from V6.1 to V7 due to the differnece in behaviour a NullPointerException gets reported incase of non-persistent messages being present in V6.1. The NullPointerException would render the destination corrupt.
Problem conclusion
The code has been modified to check for NULL that may occur during reconstitute for non-perstitent messages after migration of WebSphere Application Server from version 6.1 to higher versions. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21 and 8.0.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM43456
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-11
Closed date
2011-09-20
Last modified date
2011-09-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021