HI Ranjitha,
you want to look at the individual queue status in MQExplorer
first select queue status, the click the queue in question, on the bottom panel it will show the connection handles that are active.
So, for one of my QMGRs and the SYSTEM.ADMIN.COMMAND,QUEUE, when I took this screen shot there were 5 processes with open handles on this queue
as you move to the columns on the right you can see the userid, channel, connection name (IP address), etc
when you close the queue, you should see that instance of the MQ handle against that queue disappear.
likewise if you watch the Channel Status for the client's SVRCONN channel, you should see that instance go away when you disconnect.
------------------------------
Glen Larson
Systems Engineer Consultant - MQ
Progressive Insurance
Colorado Springs CO
------------------------------
Original Message:
Sent: Thu December 14, 2023 05:02 AM
From: Ranjitha YM
Subject: Informatica IBMMQ Connector : Queue Manager and Queue Connection close issue
Hi,
in our connector code, we have a queue manager and queue close connection code in deinit method, but after the task is complete, we verified Queue manager status, and the connection count is the same.
Ex: Before the task run, the queue manager connection count was 24
When the task running, the queue manager connection count was 26
After the task complete, the queue manager connection count was 26
After the task was completed we expected the Queue manager connection count to 24, but it not decreased.
------------------------------
Ranjitha YM
Original Message:
Sent: Wed December 13, 2023 06:22 AM
From: Francois Brandelik
Subject: Informatica IBMMQ Connector : Queue Manager and Queue Connection close issue
Hi,
If your software is attempting to consume messages from Queue 1 you need to be looking at the Open Input count.
You can also see that in the queue status.
And refresh that status often. Because if the software is opening the queue, consuming and closing the queue, the time the queue stays open may be too short for MQ Explorer to register.
If your software is a Monitoring type software, the increase in the Open Output count on the SYSTEM.ADMIN.COMMAND.QUEUE is expected as the monitoring software will use PCF messages to inquire about queues...
------------------------------
Francois Brandelik
Original Message:
Sent: Tue December 12, 2023 06:44 AM
From: Ranjitha YM
Subject: Informatica IBMMQ Connector : Queue Manager and Queue Connection close issue
Team,
We have an Informatica cloud connector for IBMMQ, The connector reads messages from the Queue and writes to the queue.
in our connector, we have code to connect to Queue Manager and Queue.
when we run a read/ write task, it opens 2 connections.
before executing the task, the Queue manager connection count was 24, when we started executing the task Queue manager connection count increased by 2. (26)
In our case Queue Manager Name is "QM_Remote" and it has Queue "QA.QUEUE.1"
we have created a connector task to read messages from Queue "QA.QUEUE.1"
when the task executing Queue Manager Connection count increased by 2 and "QA.QUEUE.1" open output count is 0
instead of "QA.QUEUE.1" queue, " SYSTEM.ADMIN.COMMAND.QUEUE" open output count increased by 2
we expected this behavior for queue QA.QUEUE.1 but open output count increased for
"SYSTEM.ADMIN.COMMAND.QUEUE"
we would like to know why this is happening.
And in our connector, we added code to close the queue manager and queue but the connection is not closing.
even after the task complete, Queue Manager and Queue ""SYSTEM.ADMIN.COMMAND.QUEUE" connection count remains the same. its not closing
------------------------------
Ranjitha YM
------------------------------