Fixes are available
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
The problem occurred in an IBM WebSphere Process Server environment, with multiple messaging clusters, and no targeting information specified on the activation specifications and connection factories. When applications were redeployed, the WebSphere Process Server deployment scripts deleted Service Integration Bus destinations, and created new ones with the same name. The following exception was thrown to applications after the dynamic redeployment was complete: CWSIC8007E: An exception was caught from the remote server with Probe Id 3-010-0003. Exception: CWSIP0471E: Unable to communicate with the messaging engine DESTINATION_HOSTING_ME where the destination DESTINATION_NAME is Localised. These applications were found to be connecting to an intermediate messaging engine, rather than the one where the destination is hosted. This was due to the environment containing multiple messaging clusters, and not having targeting information specified.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 6.1* * with a Service Integration Bus containing * * multiple members * **************************************************************** * PROBLEM DESCRIPTION: A CWSIC8007E exception or a buildup * * of messages on a remote queue might be * * observed after deleting and * * recreating a queue * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem only occurs in an environment with multiple bus members, where applications have not been configured to connect to the messaging engine that hosts the destinations that they consume from. A CWSIC8007E exception or buildup of messages might be observed on a remote queue point, when a destination has been deleted and recreated in one administrative action. For example, performing both these actions before pressing 'save' on the admin console. The problem is caused because an intermediate messaging engine erroneously updates the properties of the old remote queue point, instead of deleting the old remote queue point and creating a new one. When applications attempt to consume messages from the destination, via this intermediate messaging engine, the CWSIC8007E error occurs because the old destination is no longer available on the messaging engine that owns it. The problem can be observed by checking the UUID of the remote queue point on the intermediate messaging engine, against that of the actual UUID of the queue point on the messaging engine which hosts the destination. If the UUIDs do not match, then it is likely that this APAR has been encountered.
Problem conclusion
The fix for this APAR ensures that destinations are looked up by UUID rather than name when the intermediate messaging engine receives a dynamic configuration update, allowing it to correctly detect that the old destination has been deleted and a new destination (which happens to have the same name) has been created. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.31. 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
PM05974
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
2010-01-25
Closed date
2010-02-16
Last modified date
2010-03-12
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:
28 December 2021