PK98802: CREATING PUBLISH/SUBSCRIBE BRIDGE BROKER PROFILES TO MAKE USE OF THE WMQ 7.0 PUB/SUB ENGINE CAN RESULT IN A CWSIL0018E MESSAGE

Fixes are available

APAR status

Closed as program error.

Error description

An error similar to the following is logged when
registering a subscriber against a topic that is bridged to a
publish/subscribe broker profile where a WebSphere MQ Version
7.0 queue manager is the publish/subscribe broker:

[10/13/09 14:29:41:691 IST] 00000026 SibMessage    E   [:]
CWSIL0018E: Correlation ID
5349429E4258EB0F19FE0193304CB9000000000000000000
received in a response message from the event broker TESTQM
does not match the expected correlation ID
5349429e4258eb0f19fe0193304cb9000000000000000000 for profile
MappingProfile:
inbound = Inbound profile for brokerType=2,
topic=SportsReply,
subscriptionPoint=null,
queueManager=TESTQM,
foreignBus=ForeignBus1,
virtualQMName=WAS1,
controlQ=SYSTEM.BROKER.CONTROL.QUEUE,
ebSyntaxTopic=SportsReply,
correlID=5349429e4258eb0f19f
e0193304cb9000000000000000000
outbound = Outbound profile for brokerType=1,
topic=SportsReply,
topicSpace=TopicSpace.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server with a     *
*                  WebSphere MQ link configured with a         *
*                  publish/subscribe bridge profile pointing   *
*                  at a WebSphere MQ Version 7.0 queue manager *
****************************************************************
* PROBLEM DESCRIPTION: CWSIL0018E message logged when using    *
*                      the publish/subscribe bridge with a     *
*                      WebSphere MQ Version 7.0 queue manager  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The correlation identifier returned by the WebSphere MQ Version
7.0 queue manager does not match the correlation identifier
expected by the publish/subscribe bridge. However, this is
because the correlation identifier has been converted into an
upper-case hex string by the WebSphere MQ Version 7.0 queue
manager, whereas the publish/subscribe bridge is expecting a
lower-case hex string, and the comparison is case sensitive.

The result of this error is that the contents of the response
method will not be processed resulting in the publish subscribe
bridge ignoring it. This means that it will remain unaware of
whether the registration/deregistration of a subscriber worked
or not.

Problem conclusion

The fix for this APAR resolves the problem by updating the
publish/subscribe bridge to perform a case insensitive
comparison of the two correlation identifiers.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PK98802
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-16
Closed date
2009-11-13
Last modified date
2009-11-13

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
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK98802: CREATING PUBLISH/SUBSCRIBE BRIDGE BROKER PROFILES TO MAKE USE OF THE WMQ 7.0 PUB/SUB ENGINE CAN RESULT IN A CWSIL0018E MESSAGE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R300 PSY

Document Information

Share your feedback

Need support?