IV15811: WEBSPHERE APPLICATION SERVER V7 REPORTS A CWWMQ0045E ERROR WHEN USING ACTIVATION SPECIFICATIONS AND NON-TRANSACTED MDBS

WebSphere MQ V7.0 Fix Pack 7.0.1.9
Fix Pack 7.1.0.2 for WebSphere MQ V7.1

APAR status

• Closed as program error.

Error description

• After converting a Listener Port to an Activation Specification,
  the following error was reported in the WebSphere Application
  Server for z/OS Servant Region job-log
  when the Activation Specification detected a message:
  
  CWWMQ0045E: An internal error has occurred.
  An error, with message JMSWMQ0018: Failed to connect to queue
  manager 'qmserv' with connection mode '0' and host name
  'localhost(pppp)'., caused endpoint
  application_name#applicaion_nameEJB.jar#
  application_nam_ServiceActivatorMD to stopped
  
  A WebSphere Application Server classes for JMS trace of the
  issue shows the following error:
  
  FunctionName:
  Java_com_ibm_mq_jmqi_local_internal_base_Native_authenticate
  SourceId:
  Java_com_ibm_mq_jmqi_local_internal_base_Native_authenticate
  Category: FINEST
  ExtendedMessage:
  (Java_com_ibm_mq_jmqi_local_internal_base_Native_authenticate)
  Java_com_ibm_mq_jmqi_local_internal_base_Native_authenticate:
  MQCONN returned CC=2, RC=2058; <null>
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of:
  
  - The WebSphere Application Server for z/OS V6.1 WebSphere MQ
  messaging provider who have configured the WebSphere variable
  MQ_INSTALL_ROOT to point to a WebSphere MQ for z/OS V7
  installation.
  - The WebSphere Application Server V7 for z/OS WebSphere MQ
  messaging provider.
  - The WebSphere Application Server for z/OS V8 WebSphere MQ
  messaging provider.
  
  who have non-transacted message-driven bean applications that
  are configured to use an Activation Specification, where the
  Activation Specification has been set up to connect to a
  WebSphere MQ for z/OS queue manager using the BINDINGS
  transport with an Authentication Alias.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
  ****************************************************************
  PROBLEM SUMMARY:
  The first time an Activation Specification detects a message on
  a WebSphere MQ queue, it creates a JMS Server Session which is
  used to get the message from WebSphere MQ. The Server Session
  then passes the message onto the message-driven bean
  application that is using the Activation Specification, so that
  the message can be processed.
  
  The JMS Server Session creates a new connection to WebSphere MQ.
  It then checks whether any authentication needs to be performed
  before continuing. If authentication is required, then a user
  identifier and password are flowed down to WebSphere MQ so that
  they can be checked.
  
  If an Activation Specification is configured to use an
  Authentication Alias, the this authentication check will be
  performed using the user identifier and password in the
  Authentication Alias.
  
  After the connection has been established, and any
  authentication checks carried out, the JMS Server Session caches
  the connection to the queue manager, so that it is available for
  reuse.
  
  
  When the issue reported in this APAR occurred, the JMS Server
  Session tried to use the cached connection to the queue manager
  when performing the authentication check, before the connection
  had been cached. This caused the authentication check to fail,
  and a CWWMQ0045E error to be logged.
  

Problem conclusion

• The WebSphere MQ classes for JMS and the WebSphere MQ Resource
  Adapter (used internally by the WebSphere Application Server for
  z/OS WebSphere MQ messaging provider) have been updated so
  that, the first time a JMS Server Session is used to process to
  a message, any authentication checks are performed using the
  connection to the queue manager that has just been created,
  rather than using the cached connection.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.9
  --------           --------------------
  Windows            U200337
  AIX                U849391
  HP-UX (PA-RISC)    U849723
  HP-UX (Itanium)    U849728
  Solaris (SPARC)    U849724
  Solaris (x86-64)   U849730
  iSeries            7.0.1.9
  Linux (x86)        U849725
  Linux (x86-64)     U849729
  Linux (zSeries)    U849726
  Linux (Power)      U849727
  zOS                7.0.1.9
  
                     v7.1
  Platform           Fix Pack 7.1.0.2
  --------           --------------------
  Windows            7.1.0.2
  AIX                7.1.0.2
  HP-UX (Itanium)    7.1.0.2
  Solaris (SPARC)    7.1.0.2
  Solaris (x86-64)   7.1.0.2
  iSeries            7.1.0.2
  Linux (x86)        7.1.0.2
  Linux (x86-64)     7.1.0.2
  Linux (zSeries)    7.1.0.2
  Linux (Power)      7.1.0.2
  zOS                7.1.0.2
  
  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:

  PM59357

Fix information

• Fixed component name

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R701 PSY

     UP