MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

QM properties: ListenerBacklog and MaxActiveChannels

  • 1.  QM properties: ListenerBacklog and MaxActiveChannels

    Posted Wed April 08, 2020 06:08 AM
    Hello,

    how are related if they are the QM properties (in qm.ini) MaxActiveChannels and ListenerBacklog?

    If I define a MaxActiveChannels/MaxChannels values to 1000 and ListenerBacklog is just 400, which problems or repercussions I will get.

    Thank you in advance

    ------------------------------
    Daniel Portela Gomez
    IT Senior Consultant
    MeBro.Tec GmbH
    Böblingen
    004970317156066
    ------------------------------


  • 2.  RE: QM properties: ListenerBacklog and MaxActiveChannels

    Posted Wed April 08, 2020 08:19 AM
    The ListenerBacklog is how many connect() requests can be queued up by TCP/IP for your listener to process. If all your channels were to trying to start at EXACTLY the same time, then you might manage to hit your ListenerBacklog. In this case some of them would just go through retry processing and get in later. Once the TCP/IP connect() request has been handled by the listener and passed over to a channel pool process (amqrmppa) to run, it no longer counts toward the ListenerBacklog.

    There is no reason to make your ListenerBacklog anywhere near as big as MaxChannels. You shouldn't see any problems.

    Cheers,
    Morag

    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    ------------------------------