IV79836: MQ SSL ENABLED SDR CHANNELS STAY IN STARTING STATUS AFTER REFRESH SECURITY TYPE(SSL) IS ISSUED

APAR status

• Closed as program error.

Error description

• A queue manager is running with SSL enabled SDR and SSL enabled
  CLUSSDR channels in running state.
  When "REFRESH SECURITY TYPE(SSL) SSL" command is issued,  the
  SSL enabled SDR channels that were running
  get stuck in STARTING state.
  
  The following FFSTs with rrcE_CHANNEL_NOT_FOUND error in MQM
  Trace history may be seen:
  
  Probe Id          :- RM499012
  Component         :- rrxSecureRefreshEnv
  Program Name      :- amqrcmla
  Major Errorcode   :- STOP
  Arith1            :- 11 (0xb)
  Comment1          :- Channel failed to restart after SSL refresh
  Comment2          :- MY.SDR.CHL
  MQM Function Stack
  amqrcmla main
  rrxSecureRefreshEnv
  xcsFFST
  
  MQM Trace History
  ...
  -} xcsTerminate rc=OK
  } rrxStartChannel rc=rrcE_CHANNEL_NOT_FOUND
  { xcsBuildDumpPtr
  -{ xcsGetMemFn
  -} xcsGetMemFn rc=OK
  } xcsBuildDumpPtr rc=OK
  { xcsFFST
  
  
  Probe Id          :- RM499200
  Component         :- rrxSecureRefreshEnv
  Program Name      :- amqrcmla
  Major Errorcode   :- rrcE_SSL_REFRESH_RESTART_FAILED
  Probe Description :- AMQ9711: SSL security refresh succeeded
  but channel restarts failed.
  Comment1          :- SSL refresh failed
  MQM Function Stack
  amqrcmla main
  rrxSecureRefreshEnv
  xcsFFST
  

Local fix

• When the SDR channels are stuck in STARTING, there are two
  methods to get them started:
  
  1. Using runmqsc or equivalent MQ Explorer alternative:
  STOP CHL(MY.SDR.CHL) STATUS(INACTIVE)
  ALTER QL(XMITQ) NOTRIGGER
  ALTER QL(XMITQ) TRIGGER
  
  2.  A simple "START CHL(MY.SDR.CHL)" will also get the channel
  back up and in RUNNING status.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users issuing "refresh security type(ssl)" command when SSL
  enabled SDR and SSL enabled CLUSSDR channels are in running
  state.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The channel failed to start because the amqrcmla process was not
  able to obtain the correct channel definition to restart, due to
  an
  incorrect internal query to obtain the channel definition.
  

Problem conclusion

• The MQ refresh security routines have been modified to correctly
  query the channel definition when refreshing SSL.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.1.14
  v7.1       7.1.0.8
  v7.5       7.5.0.7
  v8.0       8.0.0.5
  
  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 LIN X86 V7

• Fixed component ID

  5724H7224

Applicable component levels

• R710 PSY

     UP