PM01244: CWSIP0181W MESSAGES ARE WRITTEN TO THE SYSTEMOUT.LOG WHEN USING SIBUS AND WEBSPHERE BUSINESS MONITOR

Fixes are available

APAR status

Closed as program error.

Error description

Two related problems can occur:

1) The following message is written to the SystemOut.log
each time a JMS queue receiver connects to a remote message
engine using WebSphere Application Server Service Integration
Bus (SIBus):

CWSIP0181W: The maximum batch size for the consumer on
destination{0}, has been set to 1.
Explanation: The destination is set to maintain message
ordering. Therefore the maximum batch size for a consumer has
been set to 1.
Action:  If ordering is not required, unset the
maintainMessageOrder attribute to disable maximum batch size
override.

2) If the first message on the destination is locked, and
strict message ordering is enabled, null is returned to the
receiver instead of an Exception.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server            *
****************************************************************
* PROBLEM DESCRIPTION: Strict message ordered destinations     *
*                      cause CWSIP0181W messages each time a   *
*                      remote client performs a synchronous    *
*                      receive, and null is returned to a JMS  *
*                      consumer when first message is locked   *
*                      on a strictly ordered destination       *
*                      instead of an exception being thrown.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1) Remote consumes are registered at the local messaging
engine as asynchronous consumers even if they are synchronous.
Because batching can occur for asynchronous consumers, and
batching can break message order, CWSIP0181W message is output
to indicate the override.  As this can happen frequently the
message should only be output once.

2) The JMS specification only allows null to be returned to
receive() if a specified timeout expires or the JMS Session is
closed.  Therefore a JMSException must be thrown to indicate
that the receive failed because strict message ordering is
enabled and the first message on the destination is locked.

Problem conclusion

The fix:

1) Suppresses the CWSIP0181W after the first occurrence,
so it is only logged once until the application server is
restarted.

2) If strict message ordering is enabled and the first message
on the queue is locked, instead of returning null to a
consumer, an Exception is thrown wrapping CWSIP0180E and or
CWSIP0194E indicating that the receive failed.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.31 and 7.0.0.11.  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
PM01244
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
2009-11-13
Closed date
2010-01-21
Last modified date
2010-01-21

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PM01244: CWSIP0181W MESSAGES ARE WRITTEN TO THE SYSTEMOUT.LOG WHEN USING SIBUS AND WEBSPHERE BUSINESS MONITOR

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

R200 PSY

Document Information

Share your feedback

Need support?