| Author |
Message
|
| sbabbar98 |
 Posted: Thu Jan 12, 2006 10:07 am Post subject: Max Size of Message ( MAXMSGL ) |
 |
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
Can someone please tell me how much is the Maximum size of message Supported in WebSphere MQ.
Default for MAXMSGL is 4194304.
I want to know what is the max which is officially supported. I understand this wil impact Network bandwith and slow doen messges if we user Large Size messages but just want to know how much is max supported by IBM.
regards
SB |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jan 12, 2006 10:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
108457600
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sbabbar98 |
| Posted: Thu Jan 12, 2006 10:31 am Post subject: Thanks |
|
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
| Thanks Jeff .. so its 100 Mb supported |
|
| Back to top |
|
|
| JT |
| Posted: Thu Jan 12, 2006 1:57 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| I understand this wil impact Network bandwith and slow doen messges if we user Large Size messages |
If this is a concern, then consider using segmented messages. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jan 13, 2006 1:53 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Use GROUPID messages to send related data between applications over more than one message.
If you increase the 4 MB default, remember to increase transmit queues, channels (sender, receiver and client as well), DLQ size and so on. |
|
| Back to top |
|
|
| jed |
| Posted: Tue Jan 24, 2006 11:27 am Post subject: |
|
|
Centurion
Joined: 08 Jan 2004
Posts: 118
Location: MI, USA
|
rule of thumb, first compute for the maximum message size that you will send and receive.
then with this, you go ahead and set the maximum message lengths on the queues, qmgr and channels.
always remember that the default maxmsgl is set to 4MB, thats for the queues, qmgr and channels.
_________________
Jed |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Jan 24, 2006 12:17 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| zpat wrote: |
Use GROUPID messages to send related data between applications over more than one message.
If you increase the 4 MB default, remember to increase transmit queues, channels (sender, receiver and client as well), DLQ size and so on. |
Don't forget to modify the qmgr and any QLocals as well.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| ashoon |
| Posted: Tue Jan 24, 2006 7:26 pm Post subject: mq channels |
|
|
Master
Joined: 26 Oct 2004
Posts: 235
|
actually it is my understanding that MQ channels do bulk message transfers vs. transferring each message at a time i.e. if I have 10,000 1K messages it will transfer 15 of those messages at once (for example). Also it has been my experience that segmented messages of smaller sizes move faster through MQ vs. one large message especially when doing multiple messages.
| mquseless wrote: |
Segmented msgs will not help, if anything it will increase the amount of data going across the channel, and the number of context switches on the channel.
For each physical message segment, a new msg has to be sent across the channel with all its baggage, i.e. XQH header and so on. It also counts as a msg for the batch size, causing more frequent confirms and commits.
A large msg is just sent as a single msg in the batch, with one XQH header, in individual msg segments down the wire. |
|
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jan 25, 2006 2:47 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Ashoon, you are referring to "batching" of messages by the channel. Each message is still transmitted indivually (and for large messages the channel will automatically "segment them", but you never see this). What the channel will do is hold off on committing the messages (ie, MQCMIT) until a "batch" is transmittd or the transmission queue goes empty..
The original parameter for controlling how many messages in a batch is BATCHSZ. Now we also have BATCHINT (waits for an empty xmit queue) and BATCHHB (checks thats the chanel is still active before batch commits) and NPMSPEED (excludes non-persistent messages from the batch).
More details on all these in the MQSC and Intercomm docs
_________________
-wayne |
|
| Back to top |
|
|
|
|
