Max node size exceeded error when testing with the DataPower probe enabled

Technote (troubleshooting)


When using the DataPower probe during the development and testing of a service, you might see errors when the service's XML Manager is configured with an inadequate "XML Bytes Scanned" property.


Errors will be seen in the DataPower logs with the text "Max node size exceeded." The transaction can fail at any point of the processing rule depending upon the amount of data being processed by the probe for the next action in the rule. An error rule will be attempted with a error-code of '0x00030009'


The DataPower probe must have the service's XML Manager property "XML Bytes Scanned" sufficiently large for the probe to be able to capture data and variables associated with the next processing action that is on the processing policy.


Development environments where the DataPower probe is utilized to debug the processing policy.

Resolving the problem

To resolve the failure, increase the value of the "XML Bytes Scanned" property to a value large enough to accommodate the XML requirements of the probe for the processing policy being tested.

Rate this page:

(0 users)Average rating

Document information

More support for:

WebSphere DataPower SOA Appliances

Software version:

4.0.1, 4.0.2, 5.0.0, 6.0.0, 6.0.1, 7.0.0

Operating system(s):


Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation