IC74662: USING A WMQ V7.0.1 MDB CLIENT APPLICATION GENERATES FFSTS WITH PROBE ID JMSCC0033 CAUSING THE FILE SYSTEM TO FILL.

WebSphere MQ V7.0 Fix Pack 7.0.1.6
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.6

APAR status

• Closed as program error.

Error description

• The WebSphere MQ v7.0.1 Resource Adapter running inside an
  application server outputs the message:
  
  JMSCC0033: A synchronous method call is not permitted when a
  session is being used asynchronously: 'deliver'
  JMSCC0033 The JMS specification does not permit the use of a
  session for synchronous methods when asynchronous message
  delivery is running.
  Create a separate session if you wish to use both synchronous
  methods and asynchronous delivery simultaneously.
  
  There is also a FFDC generated when this message is output to
  the system log files.
  
  In the case where JBoss is being used as the application
  server, this JMSCC0033 message is seen after an occurrence of
  the message:
  
  Message delivery to an MDB 'null' failed with exception:
  "The container is not started"
  

Local fix

• The JMSCC0034 and JMSCC0033 FFST can be suppressed to reduce the
  http://www-01.ibm.com/support/docview.wss?uid=swg1IZ73363
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the v7.0.1 WebSphere MQ Resource
  Adapter in an application server environment, where an
  activation specification is being used to drive a message-driven
  bean (MDB)
  from a WebSphere MQ queue.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  Using the WebSphere MQ classes for JMS, as supplied with the
  WebSphere MQ Resource Adapter (RA), within an application server
  environment to drive an MDB using an activation specification,
  when a problem occurred during MDB initialisation, the JMS
  Session associated with the MDB was
  pooled for use at a later time, containing some internal
  message identification data from the failed MDB invocation.
  
  The next time the JMS Session was taken from the pool and
  reused, a Session check detected the data from the previous
  iteration, which resulted in one of the following message being
  displayed, depending on the version of the RA in use:
  
  Versions prior to v7.0.1.3:
  JMSCC0033:
  A synchronous method call is not permitted when a session is
  being used asynchronously: 'deliver' The Java Message Service
  (JMS) specification does not permit the use of a session for
  synchronous methods when asynchronous message delivery is
  running. Create a separate session if you wish to use both
  synchronous methods and asynchronous delivery simultaneously.
  
  Versions from (and including) v7.0.1.3:
  JMSCC0034: The asynchronous delivery mechanism is in an
  inconsistent state in method: 'deliver'. An unexpected sequence
  of events has been detected during delivery of messages to a
  message-driven bean (MDB). This may be caused by client
  programming application errors. Check the application server
  log files for other problems associated with the message-driven
  bean.  Save any generated output files and use either the WMQ
  Support site:
  http://www.ibm.com/software/integration/wmq/support/, or IBM
  Support Assistant (ISA):
  http://www.ibm.com/software/support/isa/, to see whether a
  solution is already available. If you are unable to find a
  match, contact your IBM support center.
  
  
  After these messages were issued, the Sessions were again put
  back into the pool.  Subsequent usage would result in the
  message being displayed again.
  
  To the end user, the application server would appear to
  continue to process messages (providing there were still some
  'clean' server sessions in the pool), although at a reduced
  throughput rate due to the reduced number of valid Sessions
  available to process messages, which may or may not have been
  noticeable depending on the load on the server.  The
  application server's log files would continue to fill with
  these messages, for each time the dirty Session's were used
  from the pool.
  
  
  Note that this issue is a consequence of another problem with
  the MDB endpoint within the application server.  For example,
  on JBoss, the problem occurred after the following error
  condition was displayed in the logs:
  
  MQJCA4004:Message delivery to an MDB 'null' failed with
  exception: 'The container is not started'
  
  This failure to process the MDB resulted in the dirty Session
  being put into the pool.
  

Problem conclusion

• The code has been modified such that when the endpoint can not
  be created within the application server, the JMS Session is now
  discarded and a new one created when it is returned to the
  pool management system.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.6
  --------           --------------------
  Windows            U200328
  AIX                U840698
  HP-UX (PA-RISC)    U841555
  HP-UX (Itanium)    U841560
  Solaris (SPARC)    U841556
  Solaris (x86-64)   U841562
  iSeries            tbc_p700_0_1_6
  Linux (x86)        U841557
  Linux (x86-64)     U841561
  Linux (zSeries)    U841558
  Linux (Power)      U841559
  
  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:

• 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