| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MAXMSGL |
« View previous topic :: View next topic » |
| Author |
Message
|
| senMQ |
 Posted: Wed Feb 25, 2009 1:29 pm Post subject: MAXMSGL |
 |
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
We saw peculiar issue this week. One of our applications sent out messages larger than MAXMSGL. SYSTEM.CLUSTER.TRANSMIT.QUEUE accepted these messages, but the channel wasn't able to send the messages across. (This is a clustered environment) The destination (application queue) was rejecting these messages. MAXMSGL parameter is at default on all the MQ objects (queue manager, Queue & channel) We had to alter all these objects to let the messages flow normally. In this situation, ideally MQPUT should have failed. But, that didnt happen. My question is how come the messages reached the SYSTEM.CLUSTER.TRANSMIT.QUEUE even though the message size was larger than MAXMSGL. Has anyone seen this behavior in the past?
TIA |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Wed Feb 25, 2009 3:45 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The MQPUT succeeded because the MAXMSGL on the SYSTEM.CLUSTER.TRANSMIT.QUEUE was large enough to receive the message and its transmission header. That's no guarantee that the channel and destination qlocal and remote qmgr have a MAXMSGL that is large enough to handle its ultimate delivery (this occurs in separate units of work).
_________________
Glenn |
|
| Back to top |
|
|
| senMQ |
| Posted: Wed Feb 25, 2009 3:55 pm Post subject: |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
| MAXMSGL value for all the objects( QMGR, cluster channels, application & system queues) was at default, 4MB. Still, the system queues took the message but not the app ones. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Feb 25, 2009 10:48 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
if size of message on mqput was greater then maxmsglen of SYSTEM.CLUSTER.TRANSMIT.QUEUE, then the put should have failed with proper returncode. same on sending mca, if message is greater then maxmsglen on the channel it should have failed transmission and moved message to DLQ.
are you sure about the maxmsglen values? are you sure the message was routed using the MQ cluster?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| senMQ |
| Posted: Thu Feb 26, 2009 6:21 am Post subject: MAXMSGL |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
| IBM has responded that this is an issue with MQ, i.e., cluster xmitq accepting messages larger than the allowed message length. IY95538 fixes this issue. |
|
| 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
|
|
|
|
