PK01224: MQ CLIENTS LOSE TOPIC SUBSCRIPTIONS IF WAS, USING EMBEDDED MQ, IS STOPPED AND RESTARTED | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description If WAS is configured to have JMS topics that are subscribed to by clients (listeners) and WAS is stopped and restarted, it loses the registered topic subscribers. This is for WAS using embedded messaging. The client applications will not be aware of the problem. It will look to them as if there are no messages to receive. A trace of the JMS components will show something like the following: 2004-01-13 12:13:11.656000 4560 >> { com.ibm.broker.server.MQClientRecord@1aa843e0.getPublisherTopicT able 2004-01-13 12:13:11.656000 4560 >> } com.ibm.broker.server.MQClientRecord@1aa843e0.getPublisherTopicT able , {} 2004-01-13 12:13:11.656000 4560 >> } com.ibm.broker.server.ClientService@1ec043eb.isMQClientRecordEmp ty , rc=true 2004-01-13 12:13:11.656000 4560 >> { Java_com_ibm_broker_server_BrokerDatabase_deleteClient 2004-01-13 12:13:11.656000 4560 >> { ImbPubSubDatabase::pubSubDatabase 2004-01-13 12:13:11.656000 4560 >> } ImbPubSubDatabase::pubSubDatabase 2004-01-13 12:13:11.656000 4560 >> { ImbPubSubQueueDatabase::deleteClient 2004-01-13 12:13:11.656000 4560 >> { ImbResourceManager::resource ComIbmResourceManager ComIbmResourceManager , ComIbmMQConnectionManager, ComIbmResourceManager 2004-01-13 12:13:11.656000 4560 >> } ImbResourceManager::resource ComIbmResourceManager ComIbmResourceManager , ComIbmResourceManager 2004-01-13 12:13:11.656000 4560 >> { ImbMqManager::removeMessage ComIbmMQConnectionManager ComIbmMQConnectionManager , SYSTEM.BROKER.CLIENTS.DATA, 000000000000000000000000000000000000000000000000, ComIbmMQConnectionManager 2004-01-13 12:13:11.656000 4560 >> { ImbBuffer::ImbBuffer , 0, 927717128, 0Local fix Stop and restart all clients so that they can re-register to receive from this topic.Problem summary **************************************************************** * USERS AFFECTED: This problem affects customers who use the * * Embedded Messaging Server provided with * * WebSphere Application Server Version 5.x. * **************************************************************** * PROBLEM DESCRIPTION: When using the Embedded Messaging * * Server provided with WebSphere * * Application Server Version 5.x to * * perform publish/subscribe functions, * * the application server will * * occassionally lose subscription * * information following a restart. * * * * The subscribers will not be aware of * * any problem. They will just sit * * waiting for messages that never * * arrive. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem is caused by the way the Embedded Messaging Server recovers subscriptions following an application server restart. If an "unsubscribe" request has previously been issued, the recovery of subscriptions fails.Problem conclusion The fix for this APAR is currently targeted for inclusion in the JMS Cumulative Fix 5 for WebSphere Application Server. This can be downloaded from the following URL: https://www14.software.ibm.com/webapp/iwm/web/ preLogin.do?source=wsmqcsdTemporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PK01224
IBM Group: Software Group
Modified date: Jul 25, 2005
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.