PI13118: ON EITHER SIDE OF THE MQLINK, IF THE TARGET DESTINATION IS NOT FOUND, MESSAGES ARE NOT PUT IN THE EXCEPTION DESTINATION"

Fixes are available

APAR status

Closed as program error.

Error description

When a Service integration bus messaging engine connects to a
WebSphere MQ queue manager, on either side of the MQLink,
messages are not put into the exception destination when the
target destination is not found.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for                                         *
*                  IBM WebSphere Application Server V8.0 and   *
*                  V8.5                                        *
****************************************************************
* PROBLEM DESCRIPTION: In a WebSphere Application Server       *
*                      using Service Integration Bus with a    *
*                      MQLink setup, if the target             *
*                      destination is not present or is        *
*                      incorrect, then the messages are not    *
*                      put to the exception destination.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a WebSphere Application Server using Service Integration
Bus with a MQLink setup, if the target destination is not
present or is incorrect, then the messages are not put to the
exception destination. The logs indicates the following
exception -
java.lang.NullPointerException
at
com.ibm.websphere.sib.Reliability.compareTo(Reliability.java:274
)
at
com.ibm.ws.sib.processor.impl.ExceptionDestinationHandlerImpl.ch
eckMessage(ExceptionDestinationHandlerImpl.java:1871)
at
com.ibm.ws.sib.processor.impl.ExceptionDestinationHandlerImpl.ha
ndleUndeliverableMessage(ExceptionDestinationHandlerImpl.java:54
6)
at
com.ibm.ws.sib.processor.impl.ExceptionDestinationHandlerImpl.ha
ndleUndeliverableMessage(ExceptionDestinationHandlerImpl.java:49
5)
at
com.ibm.ws.sib.processor.impl.ExceptionDestinationHandlerImpl.ha
ndleUndeliverableMessage(ExceptionDestinationHandlerImpl.java:47
6)
at
com.ibm.ws.sib.comms.mq.link.MQLinkReceiver.sendToExceptionDest(
MQLinkReceiver.java:760)
From the stack trace, we observe that an attempt to send the
message to the exception destination is made, but it resulted
in a NullPointerException.

Problem conclusion

We now check for the reliability of the destination, if it is
null, then the default discard reliability would be compared
against the message reliability. If the message reliability is
Best effort Non-persistent, then the message would be
discarded. However, any other message reliability, the message
would be put to the exception destination.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.10 and 8.5.5.3. 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
PI13118
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
2014-03-06
Closed date
2014-05-30
Last modified date
2014-05-30

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:
28 April 2022

Tips

PI13118: ON EITHER SIDE OF THE MQLINK, IF THE TARGET DESTINATION IS NOT FOUND, MESSAGES ARE NOT PUT IN THE EXCEPTION DESTINATION"

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?