| Author |
Message
|
| jevirulo |
 Posted: Thu Mar 01, 2012 3:01 am Post subject: Node SOAPrequest message size limit |
 |
|
Newbie
Joined: 01 Mar 2012
Posts: 3
|
Hello,
I have a message flow with a SOAPrequest node. The WS responds to the SOAPrequest node with a message of about 21 mb (the XML hasn't attachment). In the flows's log I see the error:
2012-02-29 17:14:37.552335 ( ['MQROOT' : 0x22f39488]
(0x01000000:Name):RecoverableException = (
(0x03000000:NameValue):File = 'F:\build\S610_P\src\DataFlowEngine\ImbMqInputNode.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 2005 (INTEGER)
(0x03000000:NameValue):Function = 'ImbCommonInputNode::eligibleForBackout' (CHARACTER)
(0x03000000:NameValue):Type = 'ComIbmMQInputNode' (CHARACTER)
(0x03000000:NameValue):Name = 'REPROasincrono#FCMComposite_1_1' (CHARACTER)
(0x03000000:NameValue):Label = 'REPROasincrono.BRK-RPR-TXT-Q00' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPv610' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 2652 (INTEGER)
(0x03000000:NameValue):Text = 'Dequeued failed message. Propagating a message to the failure terminal' (CHARACTER)
Is possible that the message is too large and the node can't process it?. What is the maximum size of the message in the node SAOPrequest?
Thank you for your help, and sorry for my english  |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Mar 01, 2012 4:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
That's the last error message.
You need to look at the first error message.
Also, this is a Broker question, really. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 01, 2012 6:01 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Broker forum.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jevirulo |
| Posted: Thu Mar 01, 2012 7:20 am Post subject: |
|
|
Newbie
Joined: 01 Mar 2012
Posts: 3
|
| mqjeff wrote: |
That's the last error message.
You need to look at the first error message.
Also, this is a Broker question, really. |
There aren't more errors in the log. In the Server's Event Viewer there are "allocate memory" errors corresponding with the requests. |
|
| Back to top |
|
|
| Esa |
| Posted: Thu Mar 01, 2012 7:43 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
It seems your error logging is wired from MQInput nodes failure terminal. In general that does not make much sense. If you logged the exception from MQInput nodes catch terminal you would see the real cause of the exception.
Try the debugger. That will allow you to see the original exception. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Mar 01, 2012 12:49 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Try the debugger. That will allow you to see the original exception. |
...and if that doesn't work, take a user trace. I guarantee that you will see the full text of every exception that way. You might see a lot of other stuff that will help you, too. |
|
| Back to top |
|
|
|
|
