| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_MSG_TOO_BIG_FOR_CHANNEL on DLQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| dc01bb |
 Posted: Tue May 18, 2004 12:07 pm Post subject: MQRC_MSG_TOO_BIG_FOR_CHANNEL on DLQ |
 |
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
This is a really odd problem, that's got me stumped. Just deployed a new cluster including MQ 5.3 QMs on W2K and AIX as well as MQ 2.1 on OS/390. Cluster queue defined on OS/390. We're attempting to put messages from several of the other QM in the cluster. We see the same effect on both the W2K and the AIX QMs.
- many messages go through just fine
- certain messages wind up on the DLQ in the AIX or W2K QM with a 2188 MQRC in their MQDLH-Reason field. The odd thing is that these are NOT large messages. The original message length is 8922 which becomes 9094 when the DLH is added to it.
- when I put one of these messages, I get the following in the distributed QM log:
- AMQ9002 indicating the cluster sender to OS/390 is startng.
- AMQ9544 indicating the message is being put on the DLQ.
- on the OS/390 side, the log shows the CLUSRCVR starting (and subsequently timing out).
- Interesting to note that there doesn't appear to be a CLUSSDR with this name (TO.QDEV in this case) on the distributed queue manager.
I'm baffled. Anyone run into this?
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue May 18, 2004 12:14 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Something's not quite right.
The heading of your post says msg_too_big_for_channel which is MQRC 2218 and the one in your message reads "certain messages wind up on the DLQ in the AIX or W2K QM with a 2188 MQRC in their MQDLH-Reason field. The odd thing is that these are NOT large messages. "
If you are getting 2188, then you should probably check this from the manuals.
"Corrective action: Check the cluster workload exit to ensure that it has been written correctly. Determine why it rejected the call and correct the problem.
"
Also verify if you are at the latest CSD on all platforms, just to rule out any fixes that you are missing along the way.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| dc01bb |
| Posted: Tue May 18, 2004 12:27 pm Post subject: |
|
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
A little more digging has produced the answer to the question I think. The CLUSRCVR definition on the OS390 queue manager had a MAXMSGL of 3500. I'm not sure how this got defined this way and I won't get to talk to the people responsible until tomorrow. Nor will I get to test it with the developer since they've left for the day. I upped it to 4MB, and this should resolve the problem.
_________________
IBM Certified Specialist - MQSeries |
|
| 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
|
|
|
|
