| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How can I have MQRC_Q_FULL when putting to a remote queue? |
« View previous topic :: View next topic » |
| Author |
Message
|
| HenriqueS |
 Posted: Tue Sep 30, 2008 10:45 am Post subject: How can I have MQRC_Q_FULL when putting to a remote queue? |
 |
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Folks how can I have MQRC_Q_FULL when putting to a remote queue definition?
This means a local error or means that my partner queue (the guy who holds the destination local queue) has an error?
The only thing I see it could happen is that our XMITQ got full, but it has a big depth (100k), so I really doubt it. We are restoring some error log backups to see exactly what happened.
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Sep 30, 2008 11:36 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
There won't be anything in the MQ error logs. MQ told you at MQPUT time waht was wrong, so there is no reason to record it in the error logs.
A q filling up on a remote QM would never return a Q Full RC to your app connected to another QM.
Your XMITQ filled up. 100K is not a big depth! You can fill that in a few seconds.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Sep 30, 2008 11:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| PeterPotkay wrote: |
There won't be anything in the MQ error logs. MQ told you at MQPUT time what was wrong, so there is no reason to record it in the error logs.
|
Although if the XMITQ was full because the channel was having a problem, you would see evidence of that in the QM's error log.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Wed Oct 08, 2008 11:10 am Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
To close this case.
We realized that the communication link between us and our partner had a low speed and the XMITQ (max depth 100k) would get filled because every incoming message generated a reply from our app, plus a COA and a COD.
The test batch that they sent to us was of about 45 k messages. These messages generated 45k app replies, +45k COAs, +45K CODs.
Since the line was a poor 128kbit frame relay, the buffer (XMITQ) reached its peak level and started sending those MQRC_FULL messages...
We got into an agreement to upgrade our link speed with our partner.
Case closed.
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
