APAR status
Closed as program error.
Error description
EXTERNAL SYMPTOMS:
The only external symptom is that a WMSG0050E is logged.
Nothing fails to start or to be instantiated as a result of this
error message being logged.
MESSAGES LOGGED:
This is logged in the SystemOut.log
[4/27/05 5:18:29:991 JST] 1607ebf4 DurableSubscr W WMSG0050E:
Exception
checking JMS durable subscriptions
java.lang.NullPointerException
at com.ibm.ejs.jms.DurableSubscriptionManagerImpl.
cleanUpDurableSubscription(DurableSubscriptionManagerImpl.java:3
22)
.
If one enables the Messaging trace, one may see this logged in
the trace file.
[5/9/05 0:14:09:385 JST] 1a0e245a JMSTopicSessi e Caught
JMSException in
unsubscribe
javax.jms.InvalidDestinationException:
MQJMS3018: Unknown durable subscription
TEStore610-1.9.2.0.66#transactionware-enterprise-async-services-
store-ej
b.jar#ejb/triversity/transactionware/asyncservicessite/Configura
torUpdatesMDB
at
com.ibm.mq.jms.MQBrokerSubscriptionEngine.durableUnsubscribe(MQB
rokerSubscriptionEngine.java:2069)
RECREATION STEPS:
This problem occurs because there is a durable subscription
that is invalid. Possibly, an attempt to unregister a durable
subscription failed.
The cause of the MQJMS3018 is that durable subscriptions
have been found for topics that no longer exist. One can use
the amqsbcg utility (if it is available) to dump the queues to
see what subscriptions are held. To do this,
o Stop WAS
o Ensure the WAS queue manager is running without WAS
being active; that is, that there are no active applications or
subscribers.
o Use the MQ amqsbcg utility to dump all the
SYSTEM.BROKER.* queues and
SYSTEM.JMS.* queues.
One can then see these invalid subscriptions are seen in the
dumped queues.
SEARCH KEYWORDS:
WMSG0050E invalid durable subscription NullPointerException
NPE Null Pointer
Local fix
Customers who use WebSphere MQ as the JMS provider should
use utilities provided with that product to remove the
invalid durable subscriptions.
There is no local fix for customers who are using
WebSphere Embedded Messaging. These customers will need
to apply the Cumulative Fix or Fix Pack containing the
fix.
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the *
* Java Message Service (JMS) functionality *
* provided with WebSphere Application Server *
* Version 5 and Version 6. *
****************************************************************
* PROBLEM DESCRIPTION: When using either a message-driven *
* bean (MDB) or a Java Message Service *
* application that performs *
* publish/subscribe messaging with *
* WebSphere Application Server Version *
* 5 or Version 6, the following error *
* occurs when the application or MDB *
* shut down: *
* *
* WMSG0050E: Exception checking JMS *
* durable subscriptions *
* java.lang.NullPointerException *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If an error occurs while trying to unregister a durable
subscription, the application server will trace the original
JMS exception, followed by the linked exception. However, not
all exceptions contain a linked exception - the
NullPointerException occurs if the application server tries
to trace a linked exception that does not exist.
Problem conclusion
The DurableSubscriptionManagerImpl class has been modified to
only trace a linked exception if one actually exists.
The fix for this APAR is currently targeted for inclusion
in Cumulative Fix 13 for WebSphere Application Server Version
5.0.2, Cumulative Fix 6 for WebSphere Application Server
Version 5.1.1 and Cumulative Fix 1 for WebSphere Application
Server Version 6.0.2. Please refer to the Recommended Updates
page for delivery dates:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK08339 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-07-04 |
Closed date |
2005-07-22 |
Last modified date |
2006-09-21 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|