ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Random Q destination from client config with single Q

Post new topic  Reply to topic
 Random Q destination from client config with single Q « View previous topic :: View next topic » 
Author Message
JohnnyC
PostPosted: Wed Dec 03, 2025 10:01 am    Post subject: Random Q destination from client config with single Q Reply with quote

Newbie

Joined: 03 Dec 2025
Posts: 2

Hi,
Firstly I am sure that I will not provide all required info in this initil post.
I am relatively happy with basic MQ behaviours.

Scenario is, we have once MQ installation on Windows OS with two QMGRS (OS and MQ are relatively old and this is understood). There are three apps that connect, one through IBM WAS and JMS and the other through MQ client.
One of the apps connecting throught the client app has local config that points to QMGR and a single Q. Randomly, this app is posting to other Qs in the dedicated QMGR. At this time, I am unable to confirm from the client logging exactly which Q details are being used an whether there is any error being generated.

On the QMGR I can view the error log but nothing is showing. Based on the QMGR, can I get full connection details to show what is being sued in the request.

On this QMGR, all Qs are local, with one app putting and an app on the other side monitoring all Qs to consume the messages.
Back to top
View user's profile Send private message
hughson
PostPosted: Wed Dec 03, 2025 9:06 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1972
Location: Bay of Plenty, New Zealand

Is there a question you need answered?

I could guess that your question is "why is my application putting to random queues?" but that is certainly not a question that this forum could answer.

It is possible that your question is "why is my application putting to this specific queue when I don't expect it to?" which this forum might be able to answer when you tell us the names of the specific queues. I say this because there are some queues that get used 'under the covers' to put to or get from, that the application does not code specifically. They would show up on a
Code:
DISPLAY CONN(*) TYPE(HANDLE)

display. I am thinking specifically of SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE, SYSTEM.ADMIN.ACCOUNTING.QUEUE, SYSTEM.PROTECTION.POLICY.QUEUE and perhaps a few others.

So, you guessed right that we would likely need some more information from you.

It would also be interesting to know how you became aware that your application is using random queues if you don't know the names of those random queues? What provided the awareness of the problem in the first place?

Over to you.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
JohnnyC
PostPosted: Thu Dec 04, 2025 3:07 am    Post subject: Reply with quote

Newbie

Joined: 03 Dec 2025
Posts: 2

hughson wrote:
Is there a question you need answered?

I could guess that your question is "why is my application putting to random queues?" but that is certainly not a question that this forum could answer.

It is possible that your question is "why is my application putting to this specific queue when I don't expect it to?" which this forum might be able to answer when you tell us the names of the specific queues. I say this because there are some queues that get used 'under the covers' to put to or get from, that the application does not code specifically. They would show up on a
Code:
DISPLAY CONN(*) TYPE(HANDLE)

display. I am thinking specifically of SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE, SYSTEM.ADMIN.ACCOUNTING.QUEUE, SYSTEM.PROTECTION.POLICY.QUEUE and perhaps a few others.
Over to you.

Cheers,
Morag


Morag,
Dor sure there is a question in there but it is finding teh right way to put it across.
You are right in your initial response, the client app is putting to whatI am classing as radnon Qs. Having said random, they are Qs that exist on the QMGR. And how do we know, well we had an old Q stil on the QMGR, this was not in the config for the source app nor was it in config for the main destiantion app but the queue depth was increasing. So from this we could tell the messages origin. Also, using data from the messaegs, there is a reference number which has a sequence unique to each source app and after review, it is only this one source app that appears to be using random Qs for put rather thatn the Q in its config.

Whilst trouble shooting this is a little trickiy until we get increased logging on source app side, I am guessing that my made question is how can I determine connection string details but on the MQGR side. Currently there appears to be no error in the QMGR log, and I have looked to see if I can increase the loggign levels but these appears to not be a straight forward exercise.

JC
Back to top
View user's profile Send private message
hughson
PostPosted: Thu Dec 04, 2025 7:47 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1972
Location: Bay of Plenty, New Zealand

If your application is successfully putting to a queue name that exists and it has authority to use then there is no way for the queue manager to know that it is an error, so I would not expect to see any error in the queue manager logs. The queue manager simply did what the application asked.

I'm not sure exactly what you mean by the phrase "connection string details". To me, this phrase could mean the Connection ID that is returned to the application from the queue manager at connection time - it's looks quite like a message ID in shape and form. If that's what you mean, you can use DISPLAY CONN to view it and other things about it, like the queues it has open.

If this particular application is not supposed to be using this queue, perhaps it might be worth considering removing it's authority to use said queue?

Another alternative might be to turn on Application Activity Trace which will let you see exactly what the application is doing. You say that your queue manager platform is Windows and that the MQ version is "relatively old". Is it at least at V6? If so, AAT is available to you. Have a read of this presentation for more details.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Random Q destination from client config with single Q
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.