PI08703: MAXINSTC IS BEING HIT SINCE THE QUEUE MANAGER WAS UPGRADED FROM 7.0.1 TO 7.1.0: CSQX490E CSQXRESP MAX CLIENT INSTANCE EXCEEDED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SVRCONN consistently hitting the maximum connections limit set
  for it after upgrade to V710.
  CSQX490E M07P CSQXRESP Maximum client instance limit 300,
  exceeded, channel DEF.SERVER
  connection :xxx.xx.xx.xxx
    The change team recreated the problem and can see the cause:
  rriAcceptSessReceive is invoking ccxSetTimeOut with bHBisABSVal
  set to FALSE when a non-multiplexed client (one with SHARECNV=0,
  at the V6 level, or JMS with PROVIDERVERSION 6) has finished
  binding.
  .
  Additional Symptoms/Keywords:
    DISCINT does not work for non-multiplexed clients connecting
  to a 7.1.0 queue manager if RCVTIME=0. PM65278 indicates that
  RCVTIME applies only to message channels and MQI channels that
  use sharing conversations.
    If RCVTIME is non-zero, the timeout is the sum of DISCINT
  and RCVTIME rather than just being the DISCINT value.
  .
  CSQX489E Maximum instance limit exceeded
  CSQX513E Current channel limit exceeded
  

Local fix

• Set RCVTIME, for example
    /cpf ALTER QMGR RCVTIME=60 RCVTTYPE=ADD
  where "cpf" is the command prefix for the queue manager.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: SVRCONN channels with SHARECNV(0) do    *
  *                      not disconnect after the disconnect     *
  *                      interval (DISCINT) has elapsed.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a queue manager has RCVTIME=0 and RCVTTYPE=MULTIPLY then the
  xGwa.fRcvTimeoutOn is set to zero.
  When rriAcceptSessReceive starts a SVRCONN channel which has
  SHARECNV set to zero then it calls ccxSetTimeOut passing a
  bHBisABSVal=FALSE, but because xGwa.fRcvTimeoutOn is set OFF
  then the DISCINT of the channel is ignored and the channel stays
  running forever.
  

Problem conclusion

• rriAcceptSessReceive has been changed so that the DISCINT
  value is heeded for a SVRCONN channel with SHARECNV(0) if
  RCTYPE=0 and RCVTTYPE=MULTIPLY.
  100Y
  CMQXRMSA
  

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:

  IV55376

Modules/Macros

• CMQXRMSA
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R100 PSY UI15333

     UP14/04/09 P F404

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.