| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Limit on message size for MRM parser (delimited) |
« View previous topic :: View next topic » |
| Author |
Message
|
| kegriffi |
 Posted: Thu Jan 22, 2004 10:22 am Post subject: Limit on message size for MRM parser (delimited) |
 |
|
Newbie
Joined: 22 Jan 2004
Posts: 4
|
| I am using the mrm parser to parse inbound messages that are just a delimited string.. have been for a year and a half.. now am starting to get larger messages.. is there a limit on the size of message that can be parsed? When these messages exceed 1K the execution group is abending.. Production issue.. any prompt response would be greatly appreciated. |
|
| Back to top |
|
 |
| Lisa |
| Posted: Thu Jan 22, 2004 10:41 am Post subject: 1K |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Please post your error messages.
Lisa |
|
| Back to top |
|
|
| kegriffi |
| Posted: Thu Jan 22, 2004 1:35 pm Post subject: Limit on message size for MRM parser (delimited) |
|
|
Newbie
Joined: 22 Jan 2004
Posts: 4
|
Thanks for the reply..
Jan 22 14:28:32 wmsbck01 WMQIv210[10854]: (MQSIDEV.KGG)[10]BIP2228E: Severe error: /build/S210_P/src/CommonServices/Unix/ImbAbend.cpp 417 signal received Abend file: /var/wmqi/errors/MQSIDEV.KGG.10854.10.abend action: abort
Jan 22 14:28:32 wmsbck01 WMQIv210[17407]: (MQSIDEV)[6]BIP2060W: The broker has detected that the Execution Group KGG, process ID 10854, has shutdown. : MQSIDEV.agent: /build/S210_P/src/AdminAgent/ImbAdminAgent.cpp: 3789: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Actually I found out the problem.. It is not a limit in the parser.. it had to do with me putting too much up in the environment.. I ws selecting several messages up from a database and parsing them one at a time.. the larger messages just pushed it over the limit I guess.. i switched to just selecting up the keys and looping thru those, then getting the messages one at a time from the database.. this works fine.. more database hits, but at least it works.. |
|
| Back to top |
|
|
| MikeC |
| Posted: Wed Sep 15, 2004 11:07 am Post subject: |
|
|
Acolyte
Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada
|
I just had this exact error occur in my production system too.
Can you elaborate on your solution a little? What do you mean by "..putting too much up in the environment."? When you say "..the larger messages pushed it over the limit.." what do you mean exactly? .. Pushed what over the limit?
Our messages aren't taken from a database, they're pulled directly off a queue, but the error appears to be identical.
Thanks very much.
_________________
-Mike. |
|
| Back to top |
|
|
| kegriffi |
| Posted: Wed Sep 15, 2004 12:08 pm Post subject: message size.. |
|
|
Newbie
Joined: 22 Jan 2004
Posts: 4
|
Mike.. As you know there are several memory structures, for lack of a better word that are associated w/ a flow.. LocalEnvironment, Environment, ExceptionList, Root.. and so on.. we were doing a select that returned a large number of rows which we were storing in the Environment.. was basically the result set from the select stored as repeating xml segments.. this was so larg that we were running out of stack space.. we solved it by making the select return just the rowid and then as we looped thru the result set, we retrieved the rowid and issued a select to return only the values we needed from that row.. this kept us from carrying around that large amount of data in the Environment
Hope this helps |
|
| 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
|
|
|
|
