| Author |
Message
|
| suneel |
 Posted: Tue Jan 18, 2011 2:04 am Post subject: MQRC 2042 |
 |
|
Voyager
Joined: 06 Nov 2009
Posts: 89
|
Hi,
When i am posting messages on remote queue message are lying in transmit queue. SDR channel is in retrying status i got below error from logs
01/18/11 09:48:00
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'XP.XM.FLASHT_NCAS07T1.B' on queue manager 'XP.QM.FLASHT' failed with reason
code 2042.
ACTION:
Ensure that the queue is available and retry the operation. |
|
| Back to top |
|
 |
| fatherjack |
| Posted: Tue Jan 18, 2011 2:38 am Post subject: Re: MQRC 2042 |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| suneel wrote: |
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'XP.XM.FLASHT_NCAS07T1.B' on queue manager 'XP.QM.FLASHT' failed with reason
code 2042.
ACTION:
Ensure that the queue is available and retry the operation. |
And did you try to find out what 2042 means and then fix it and then retry the operation as the error message suggests?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| WBI_User21 |
| Posted: Tue Jan 18, 2011 5:19 am Post subject: |
|
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
XMIT Queue might have being exclusively opened by Channel initiatior which is dead . But Phantom process of CHIN might be still holding the xmit queue not allowing any new connections ..
_________________
Ranga |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jan 18, 2011 7:11 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| WBI_User21 wrote: |
| XMIT Queue might have being exclusively opened by Channel initiatior... |
Then he's got real problems because it's normally the MCA that does that 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 18, 2011 8:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Applications should never explicitly MQOPEN an xmitq. Rather, apps should open QRemote definitions.
The MCA will open-exclusive on the xmitq. Why is your app opening the xmitq for input?
_________________
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 |
|
|
| santnmq |
| Posted: Tue Jan 18, 2011 9:25 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
check-out if there is any process running on this queue, get the details about that process. If it is any process related to application, it should not directly run on xmitq.
Also check for any FDCs generated with this issue. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 19, 2011 2:17 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| santnmq wrote: |
check-out if there is any process running on this queue, get the details about that process. If it is any process related to application, it should not directly run on xmitq.
|
If an app correctly opens a remote queue definition that resolves to the XMITQ, or specifies a destination queue and queue manager name that resolves to the XMITQ, then there will be a process directly connected to the XMITQ. There's now way to tell if the app opened the XMITQ directly or not just by looking at what has that XMITQ open.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Jan 19, 2011 2:34 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
IMHO the discussion goes into a wrong direction. nobody (or the poster) said that he is opening the xmitq directly. he said he is putting messages to remote queue. even if he where putting to the xmitq directly, he would not get 2042, as he is doing output, but the "exclusive" is related to input. in addition, the 2042 is not related to his mqput, as he may received the returncode directly in the program, it would not have been visible in the amqerrxx.log.
i also dont think that this is some kind of a "dead" mca.
i suspect this is just a bad mq configuration. maybe an xmitq that is by mistake used by 2 channels, and second channel failed to start as first channel already opened the xmitq exclusive.
maybe somehting like that.
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
