PK70064: NULLPOINTEREXCEPTION EXCEPTION USING BEST EFFORT OR EXPRESS NONPERSISTENT MESSAGES WITH A REMOTE MEDIATION POINT

Fixes are available

APAR status

Closed as program error.

Error description

The problem occurred with a remote mediation point (the
Mediation Point belongs to a different messaging engine than the
associated Queue Point) and a Best Effort NonPersistent or
Express NonPersistent message is mediated on
that mediation point. The result was a NullPointerException.

Local fix

The non-persistent code path is altered so that a queue point
will not be assumed to be available on the local messaging
engine (local to the remote mediation point).

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for WebSphere Application Server v6.1       *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException is seen when a   *
*                      remote mediation point is invoked       *
*                      for a best-effort or express            *
*                      monpersistent message, preventing       *
*                      messages from being delivered to the    *
*                      mediated destination.                   *
*                                                              *
*                      A mediation point is remote, if the     *
*                      mediation point is on a different       *
*                      messaging engine to the queue point     *
*                      that is mediated (the location          *
*                      where the mediation code itself runs    *
*                      is not relevant).                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the failing scenario, messages were being delivered to the
mediation point for the destination via another messaging
engine. The following FFDC occurred showing the
NullPointerException, which prevented messages from being
delivered to the mediation point:

Stack Dump = java.lang.NullPointerException
 at
com.ibm.ws.sib.processor.impl.PtoPInputHandler.
   deliverExpressMessage(PtoPInputHandler.java:1969)
 at
com.ibm.ws.sib.processor.gd.ExpressTargetStream.writeValue(Expre
ssTargetStream.java:154)
 at
com.ibm.ws.sib.processor.gd.TargetStreamManager.handleMessage(Ta
rgetStreamManager.java:199)

This will only occur when using best effort or express
nonpersistent messages and that Mediation Point is located on
a separate messaging engine to the associated Queue Point.

Problem conclusion

This APAR solves the problem.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.21.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Use a message reliability higher than express nonpersistent,
or locate the Mediation Point on the same messaging engine as
the Queue Point.

Comments

APAR Information

APAR number
PK70064
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
2008-08-04
Closed date
2008-09-05
Last modified date
2008-09-05

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

PK70064: NULLPOINTEREXCEPTION EXCEPTION USING BEST EFFORT OR EXPRESS NONPERSISTENT MESSAGES WITH A REMOTE MEDIATION POINT

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?