Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
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
An attempt to delete a WebSphere Application Server v6.1.x Service Integration Bus(SIB) destination fails and the destination remains in DELETE_PENDING state. There are locked messages on the destination. A messagestore dump of the JVM hosting the messaging engine shows the following exception occurs when SIB attempts to remove the messages: java.lang.NullPointerException com.ibm.ws.sib.processor.impl.destination.JSPtoPRealization. onExpiryReport(JSPtoPRealization.java:1501) com.ibm.ws.sib.processor.impl.BaseDestinationHandler.event MessageExpiryNotification(BaseDestinationHandler.java:3650) com.ibm.ws.sib.processor.impl.BaseDestinationHandler.message EventOccurred(BaseDestinationHandler.java:3557) com.ibm.ws.sib.processor.impl.store.items.MessageItem.event ExpiryNotification(MessageItem.java:855) com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.expirable Expire(AbstractItemLink.java:1782) com.ibm.ws.sib.msgstore.expiry.Expirer.alarm(Expirer.java:445) com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) The following message is written to the SystemOut.log: CWSIP0063I: The local destination XXX with UUID ############### has been marked for deletion.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: A destination is stuck in * * delete_pending state even when all * * indoubt transactions have been * * completed. * **************************************************************** * RECOMMENDATION: * **************************************************************** A destination that was deleted is still present in the messaging engine and has a state of delete_pending. The reason for this is because there are one or more messages still on the destination that are not in an available state. This APAR solves the problem when the message was in an expiring state but can not be expired due to the following exception: java.lang.NullPointerException com.ibm.ws.sib.processor.impl.destination.JSPtoPRealization. onExpiryReport(JSPtoPRealization.java:1501) com.ibm.ws.sib.processor.impl.BaseDestinationHandler.event MessageExpiryNotification(BaseDestinationHandler.java:3650) com.ibm.ws.sib.processor.impl.BaseDestinationHandler.message EventOccurred(BaseDestinationHandler.java:3557) com.ibm.ws.sib.processor.impl.store.items.MessageItem.event ExpiryNotification(MessageItem.java:855) com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.expirable Expire(AbstractItemLink.java:1782) com.ibm.ws.sib.msgstore.expiry.Expirer.alarm(Expirer.java:445) com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) The destination in delete_pending state does not cause a functional problem, as a new destination with the same name can still be created, and no new messages would be sent to this destination that is in delete_pending state.
Problem conclusion
This APAR will allow the message to expire which will then allow the destination to complete the deleting processing. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.41 and 7.0.0.19 . 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
PM36469
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-07
Closed date
2011-05-31
Last modified date
2011-08-03
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
PLAT MSG COM
Fixed component ID
620600101
Applicable component levels
R200 PSY
UP
Document Information
Modified date:
27 October 2021