IC63539: WMQV7: MS0T MQEXPLORER FAILS TO CONNECT TO A REMOTELY ADMINISTERED QUEUE MANAGER WHEN USING A JAVA SECURITY EXIT

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

• When configuring the WebSphere MQ (WMQ) Explorer (MS0T
  SupportPac) to use a Java security exit, the WMQ Explorer
  hangs. The WMQ Server reports in the main error logs a constant
  connection issue with error:
  
  AMQ9208: Error on receive from host 'HOSTNAME'
  (999.99.999.99).
  EXPLANATION:
  An error occurred receiving data from 'HOSTNAME'
  (999.99.999.99) over TCP/IP. This may be due to a communications
  failure.
  ACTION:
  The return code from the TCP/IP (read) call was 131 (X'83').
  Record these values and tell the systems administrator.
  

Local fix

• Use a security exit written in C.  Follow the instructions below
  to invoke the exit:
  1. Start the 'Add Remote Queue Manager...' wizard and complete
  panel 1 and panel 2.
  
  2. On panel 3 select the 'Enable security exit' checkbox.
  
  3. In the 'Exit name:' field enter the full path to the library
  which contains the exit (excluding the .dll extention), followed
  by the name of the method to call in brackets (e.g.
  C:\path\library(METHODNAME)
  
  Please be careful when entering the path because if there is an
  error, you will run into the problem of the Explorer hanging.
  4. Clear the default entry in the 'in directory' field and
  replace it with a single space character.  This is only
  necessary to enable the 'Finish' button on the wizard.
  5. Click the 'Finish' button and the Explorer should load the
  exit and connect to the queue manager.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users connecting the MQ Explorer to a queue
  manager using a client-side channel security exit.
  
  Platforms affected:
  Linux (x86),Linux (x86-64),Windows
  
  ****************************************************************
  PROBLEM SUMMARY:
  Synchronization was introduced to maximise sharing of
  connections. If an exception was thrown when trying to load a
  security exit, the code which notifies any waiting thread was
  being skipped.  This meant that the waiting thread would sleep
  forever, causing the client which was trying to connect to hang.
  

Problem conclusion

• Threads waiting for the connection to complete are now notified,
  even if an error occurs while loading the exit.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.1
  --------           --------------------
  Windows            U200310
  Linux (x86)        U826321
  Linux (x86-64)     U827231
  
  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