You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw that the exporter application connects to the QMGR and opens 5 handles by queue (subscribe to each metric like openclose, put, get, inqset, conndisc). As we have environments with hundreds of queues, we had a problem with de maxhands parameter of the qmgr, that needed to be strongly increased.
It may represent some problem, because we had to alter the maxhands to 2100 and it opens the possibility to other applications to work in a innapropriated behaviour, like a looping of handles in some queues.
Other problem is that as the number of queues grow, we need to increase de maxhands parameter too.
Do we have anyway to alter the application logic so it opens (for example) the limit of 250 handles per connection? In that way, we would never have to alter the maxhands of the qmgr.
Using this example, the application could establish a connection with the qmgr and starts to open the handles. If the number of handles reaches 250, the application establishes a new connection and starts to open new handles with this new connection, and so on.
Hope I made myself clear, guys :D
If I need to explain something else, just say so :)
Kind regards,
Alex
The text was updated successfully, but these errors were encountered:
Hi @AlexAlvesJr I think I found problem as you mention, in my environment I increase maxhands from 256 (Default) to 625 due to I need to monitor more object in MQ.
My system found error that they cannot create more process and generate many dump log (FDC) until file system full.
I think it's because of maxhands parameters, some application retry to MQ with wrong config and retry every 10 secs.
Hello guys!
I saw that the exporter application connects to the QMGR and opens 5 handles by queue (subscribe to each metric like openclose, put, get, inqset, conndisc). As we have environments with hundreds of queues, we had a problem with de maxhands parameter of the qmgr, that needed to be strongly increased.
It may represent some problem, because we had to alter the maxhands to 2100 and it opens the possibility to other applications to work in a innapropriated behaviour, like a looping of handles in some queues.
Other problem is that as the number of queues grow, we need to increase de maxhands parameter too.
Do we have anyway to alter the application logic so it opens (for example) the limit of 250 handles per connection? In that way, we would never have to alter the maxhands of the qmgr.
Using this example, the application could establish a connection with the qmgr and starts to open the handles. If the number of handles reaches 250, the application establishes a new connection and starts to open new handles with this new connection, and so on.
Hope I made myself clear, guys :D
If I need to explain something else, just say so :)
Kind regards,
Alex
The text was updated successfully, but these errors were encountered: