| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Problem with Application segmentation |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Wed May 16, 2007 7:23 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'd guess (in the absence of an error code) that the max msg length is 4Mb so it reassembled the segmented message (2 * 2.2 Mb as you say),did it's thing, tried to write the message out and blew.
But that's just a guess.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| nab054371 |
| Posted: Wed May 16, 2007 8:28 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2006
Posts: 173
|
| that does not seem to be the case.I get 2030 on MQOUTPUT node,which means it does not seem to be segmenting the message at all,after i uncheck segmentation allowed on thatnode... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 16, 2007 11:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nab054371 wrote: |
| that does not seem to be the case.I get 2030 on MQOUTPUT node,which means it does not seem to be segmenting the message at all,after i uncheck segmentation allowed on thatnode... |
No, that's exactly what I mean. It's taken 2 segments at 2.2Mb, processed them, tried to write them out as a single 4.4Mb (because segmentation is not allowed) and blows with a 2030 (MQRC_MSG_TOO_BIG_FOR_Q).
This is the scenario I was thinking of. Sorry if I failed to articulate it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
