| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Huge Messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| cots |
 Posted: Tue Sep 09, 2003 7:39 am Post subject: Huge Messages |
 |
|
Centurion
Joined: 16 Jun 2003
Posts: 105
|
We have huge documents(~ 2-3 gag.) and would like to use MQ as its deliverying machnism. My questions are
1 what is the maximum message length on windows2000 environment and HP environment?
2. what is minimum of memory requirement for those setting?
3. If MQ can not handle such big file in one message, is there any other way to get around this problem?
thanks in advance |
|
| Back to top |
|
 |
| mgrabinski |
| Posted: Tue Sep 09, 2003 9:25 pm Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
As far as I remember, the limit is 100MB for both platforms.
You have 2 options -
1) automatic segmentation (MQPMO_ALLOW_SEGMENTATION at sending side and MQGMO_COMPLETE_MSG at the reciveing end). This may require huge appliaction buffers. Be carefull
2) reference messages - a message contains only description of the file being sent, and the file itself is written directly to disk.
I have a project where 10GB files are sent from HP to z/OS. Since MQ on z/OS doesn't support neither of the above techniques, we have to divide and assemble the files programmatically.
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Sep 10, 2003 6:50 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Option 2 can work, but the sending application still has to have some smarts. It needs to send multiple reference messages, that each specify an offset in the file that needs to be transferred, and probably a length. This is because in order to use reference messages you have to write channel exits at the sending and receiving ends that take the data from disk into a message, and put it back to disk from a message. These exits cannot handle sending multiple messages over the channel, for one reference message. The data is still transfered in a message that has to adhere to MQSeries restrictions of Max Message Size in the Channel. 
I think the only viable option is the solution you are using. The application must slice and dice the message, and the receiver must re-assemble.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
