IC60714: ENDPOINT IS NOT STOPPED IF MDB ROLLS BACK A MESSAGE, EVEN IF WAS_STOPENDPOINTIFDELIVERYFAILS, WAS_FAILUREDELIVERYCOUNT IS SET

WebSphere MQ V7.0 Fix Pack 7.0.1.1
WebSphere MQ V7.0 Fix Pack 7.0.1.2

APAR status

• Closed as program error.

Error description

• EndPoint is not stopped if the MDB rolls back a message,
  There are no exceptions reported from the onMessage method even
  if the "Stop endpoint if message delivery fails" and "Number of
  sequential delivery failures before suspending endpoint"
  attributes are set for the Activation Specifications, in
  Websphere Application Server.
  .
  Suspending the Endpoint is triggered from the WMQ RA when the
  "deliveryFailed method" is called. This occurs only on an error.
  This seems to be the primary reason why the Endpoint is not
  getting suspended.
  .
  A RuntimeException needs to propagate out of onMessage() or an
  internal WMQ exception must occur for the WMQ RA to initiate the
  WebSphere Application Server container to stop/suspend the
  Endpoint.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WebSphere Application Server V7
  WebSphere MQ messaging provider who have MDBs configured to use
  Activation Specifications.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  The WebSphere Application Server V7 WebSphere MQ messaging
  provider uses the WebSphere MQ V7 Resource Adapter (RA) to
  communicate with queue managers.
  
  Suspending endpoints was triggered from the RA when the
  "deliveryFailed" method is called. This only used to happen if
  either the RA received an exception from an MDB's onMessage()
  method, or an internal exception occurred. The endpoint was not
  stopped if an MDB simply rolled back a message a number of
  times.
  

Problem conclusion

• The WebSphere Application Server V7 WebSphere MQ messaging
  provider currently has the ability to pause a MDB if
  message delivery fails (for example, if onMessage() generates a
  RuntimeException). This has now been extended to include the
  situation where the transaction under which the message was
  delivered to the MDB is rolled back.
  
  This change means that the WebSphere Application Server V7
  WebSphere MQ messaging provider Activation Specification
  support is equivalent to that of Listener Ports.
  
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.0
  --------           --------------------
  Windows            U200306
  AIX                U823774
  HP-UX (PA-RISC)    U823665
  HP-UX (Itanium)    U823667
  Solaris (SPARC)    U823772
  Solaris (x86-64)   U824344
  iSeries            tbc_p700_0_1_0
  Linux (x86)        U823664
  Linux (x86-64)     U823773
  Linux (zSeries)    U823668
  Linux (Power)      U823666
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK84312

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WMQ WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP