| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tracking Application messages from MQ Channel connections |
« View previous topic :: View next topic » |
| Author |
Message
|
| nimmismailbox |
 Posted: Mon Nov 19, 2018 1:50 am Post subject: Tracking Application messages from MQ Channel connections |
 |
|
Newbie
Joined: 19 Nov 2018
Posts: 1
|
Hello,
I have a particular scenario where a Seibel (COTS) application connects to MQ via a MQ server connection channel in a shared environment. The max channel instances and max instances per client for the channel is set to 50. The version of MQ used is 8.0.0.2.
There is a strange issue where the application is using up all the connections during one of the server restarts leading to errors. They are unable to identify the thread/process which connects to the channels using the Connection id, Connection name,Thread id etc which is displayed in the Queue manager application connections. But they would like to identify which of the channel instances are connected to which of their threads/listeners to troubleshoot why the respective channels are not being freed.
So far during our research, we have identified Connection name , MCA Userid, Thread, Connection id. But this dint seem to help much as they have several processes/listeners within each server.
Is there any way to track more details about the clients connecting to the MQ.
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 19, 2018 7:15 am Post subject: Re: Tracking Application messages from MQ Channel connection |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nimmismailbox wrote: |
| They are unable to identify the thread/process which connects to the channels using the Connection id, Connection name,Thread id etc which is displayed in the Queue manager application connections. |
What do they use to identify the thread / process? Thread id seems fairly unique to me.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tczielke |
| Posted: Mon Nov 19, 2018 1:26 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
What I recommend our MQ client applications to do is to set the APPNAME attribute on their MQ connection to something unique to their application (or process). If the MQ client applications follow this requirement, the MQ admin is then be able to see this application value when you do a DIS CONN (under APPLTAG) or DIS CHSTATUS (under RAPPLTAG) on the MQ queue manager side.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Nov 19, 2018 3:05 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Can each thread/process/listener (or small set of them) be configured to use their own server connection channel (SVRCONN)? The name should indicate the logical function or instance. This will help identify usage patterns and behaviour.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
