Author |
Message
|
Coltrane |
Posted: Sat Feb 11, 2006 5:28 pm Post subject: MQInput and large messages > 200MB |
|
|
Newbie
Joined: 11 Feb 2006 Posts: 2
|
We have a need to process message that can be as large as 220MB, but it is unclear to me exactly what options I need to set in the MQInput node to successfuly process such large messages.
All messages are persistent, and will be segmented by the source queue manager at 100MB.
What MQInput options will I need to configure and how, and is there any coding/setting that I would be conplete within my message flow ?
Environment: WBIMB 5.0 |
|
Back to top |
|
 |
jbanoop |
Posted: Sat Feb 11, 2006 11:01 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005 Posts: 401 Location: SC
|
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Feb 12, 2006 5:36 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
And you might consider segmenting at 4MB instead of 100 MB. A lot less defaults to change on sending and receiving qmgrs....
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
ashoon |
Posted: Sun Feb 12, 2006 6:40 pm Post subject: curious about your message |
|
|
Master
Joined: 26 Oct 2004 Posts: 235
|
I'd like to get a feel for the solution you're designing that will require such a large message input... I've never seen a message input larger than 1MB - is it b/c that message is made up of multiple transactions - if so why not send it a transaction at a time? |
|
Back to top |
|
 |
wschutz |
Posted: Mon Feb 13, 2006 8:32 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Lets hope he has lots of real memory available and low expectations for throughput .... _________________ -wayne |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Feb 13, 2006 8:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Yeah. It's probably a real good idea to put the flow that has to handle these in it's own EG. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Coltrane |
Posted: Mon Feb 13, 2006 4:35 pm Post subject: Problem Background |
|
|
Newbie
Joined: 11 Feb 2006 Posts: 2
|
The large message represents finanical (reconciliation data) that can grow to 220MB depending on very heavy trading volumes. These sizes was made known after the implementation was completed and Pre-Production testing was well underway.
Processing time SLA is that the data should be delivered within 4 hours.
The data provider has chosen to segment the messages at 100MB and has not engaged us in any of these decisions. We are being asked to potentially process messages as large as 220MB.
Hope this helps. |
|
Back to top |
|
 |
|