Author |
Message
|
doubtmaster |
Posted: Tue Oct 02, 2012 12:01 pm Post subject: Xmitq with source QMGR, msgs increasing |
|
|
Newbie
Joined: 02 Oct 2012 Posts: 5
|
Hello All,
we have a problem in our support project architecture. We found one xmitq curdepth is increasing. We checked for channel but no channel is using it.
this Xmitq is created with the source qmgr name only.
Someone help me why an xmitq created like that and under use. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 02, 2012 12:08 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Someone is using the name of the queue manager to address messages. That's why they're getting put to the xmitq. |
|
Back to top |
|
 |
doubtmaster |
Posted: Tue Oct 02, 2012 12:43 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2012 Posts: 5
|
But, in our architecture they are using FTF v4 (PM4 data), is it using ?
Till 2 days before we didn't face this issue. now suddenly it is happening. Application team people saying they are inititating the right requests only. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 02, 2012 1:06 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Look at the connection handles on the queue, find out what process has it open for writing.
Something is addressing messages using the name of this xmitq as either the name of a queue or the name of a queue manager.
See if the messages on the queue have a transmission header on them. If they do, you know it's because someone is trying to use the name of the queue as the name of a queue manager. If they don't, it's because someone is using it as the name of a queue. |
|
Back to top |
|
 |
doubtmaster |
Posted: Tue Oct 02, 2012 1:51 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2012 Posts: 5
|
We couldn't check the QSTATUS for finding the processes connected. i think xmitq never let us see the handles
checked the header and it started with XQH but not sure who is keeping these msgs and who created this queue without channel association. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Oct 02, 2012 2:09 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
An XQH tells us that the app mqopened a QRemote definition. Look for the original MQMD and application data in the xmitq.
You could put disable the xmitq, then wait for someone to call to complain. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Oct 02, 2012 2:44 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
bruce2359 wrote: |
An XQH tells us that the app mqopened a QRemote definition. |
Or they didn't use a Remote Q definition but instead supplied both the destination QM and destination Q in the MQOPEN / MQPUT1.
doubtmaster wrote: |
this Xmitq is created with the source qmgr name only.
|
The source QM? The XMITQ on QM1 is called QM1? Or did you mean the destination QM? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
doubtmaster |
Posted: Tue Oct 02, 2012 3:27 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2012 Posts: 5
|
Yes both QMGR and XMITQ having same name. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Oct 02, 2012 3:35 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Ooooh, ooooh!
Does the qmgr object default xmitq attribute specify an xmitq name? And is that name also the same name as the qmgr? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Tue Oct 02, 2012 3:36 pm; edited 1 time in total |
|
Back to top |
|
 |
doubtmaster |
Posted: Tue Oct 02, 2012 3:36 pm Post subject: |
|
|
Newbie
Joined: 02 Oct 2012 Posts: 5
|
Yes they have remoteq with this xmitq configured inside. It was created back in 2010. Till now no issues...
Didn't find MQMD in msg header....
Edit by exerk: Following two duplicate posts removed. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Oct 02, 2012 3:40 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
A message in an xmitq should contain an XQH (with its own MQMD), and your original application-created MQMD and application data.
Display a few complete messages from the xmitq (with amqsbcg, or equivalent). You may suppress proprietary application data - we don't need to see that. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Oct 02, 2012 6:25 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
In addition to what bruce requested...
What is your exact QM name?
On this same QM, what is the exact XMITQ definition that you are questioning? Post the whole definition from a runmqsc command.
What you have said so far is the QM name is something like APPLE, and you are saying the XMITQ on the APPLE QM is aslo called APPLE, and that it has been like this since 2010, and things have been fine. This cannot be. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|