| Author |
Message
|
| Vitor |
 Posted: Thu Dec 14, 2006 2:30 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It sounds like you're heading for a PMR to me.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Thu Dec 14, 2006 6:13 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Kristoffer wrote: |
When trying to start it we received this error:
"The MQOPEN call failed. The queue manager issued an MQOPEN call to open a WebSphere MQ object. The call failed. Check the queue manager's error log for more information about the error. (AMQ4063)"
I haven't found anything suspicious in the queue managers error logs. The only entriers for this particular channel are normal start/end ones. |
You aren't dropping messages directly onto the transmission queue from your application are you? |
|
| Back to top |
|
|
| Kristoffer |
| Posted: Thu Dec 14, 2006 6:49 am Post subject: |
|
|
Novice
Joined: 21 Nov 2006
Posts: 15
Location: Sweden
|
| Quote: |
You aren't dropping messages directly onto the transmission queue from your application are you? |
Nope, the "path" is like this:
- Broker puts message to remote queue definition on QM1
(Remote definition has XMITQ(QM2) RQMNAME(QM3), the remote queue do exist and most of the messages actually do arrive)
- Message arrives at QM2, where XMITQ for QM3 resides. |
|
| Back to top |
|
|
| bbburson |
| Posted: Thu Dec 14, 2006 6:57 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| Sounds like the QM3 transmit queue may be corrupted. Are there messages on that queue? Can it be rebuilt? |
|
| Back to top |
|
|
| Kristoffer |
| Posted: Mon Feb 05, 2007 1:37 am Post subject: [SOLVED] Messages seems to dissappear in transit between QM |
|
|
Novice
Joined: 21 Nov 2006
Posts: 15
Location: Sweden
|
This problem has been solved. I would like to thank everybody for all the great input on possible causes.
The problem was that we had another sender channel on the queue manger that had this transmission queue specified. The two channels were "fighting" over each message that landed on the XMITQ, hence the "works sometimes" behaivour. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 05, 2007 4:07 am Post subject: Re: [SOLVED] Messages seems to dissappear in transit between |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Kristoffer wrote: |
This problem has been solved. I would like to thank everybody for all the great input on possible causes.
The problem was that we had another sender channel on the queue manger that had this transmission queue specified. The two channels were "fighting" over each message that landed on the XMITQ, hence the "works sometimes" behaivour. |
If you have multiple channels using the same Xmitq (sometimes a legitimate setup) you HAVE to specify the trigdata on the Xmitq if the xmitq is triggered. Otherwise the first occurrence of the channel using the xmitq is triggered.
Of course both channels cannot run concurrently. And they should ultimately have the same destination -- just going a different route-- (multihopping a different way if the next usual hop is not available....).
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
