Dear all,
until today this was also my understanding, how the message size limit works and that you can specify it at different levels.
In the past we were working with the "Message Size Limit" assertion within the policy if it needs to handle larger requests than the default 2,5MB, e.g. 5MB. This was working fine.
Now we need to configure this behavior to a new policy, where it is NOT working.
I must learn from this
article, that the assertion within the policy can only be stronger than the CWP, but not the other way round.
I checked this with some tests and can at least confirm this behavior.
Therefor I have the following two questions:
1. Why it is working for other policies? Is there any additional difference/setting? For your reference, we have disabled the "Perform WS-Security" option.
2. What is the correct method to allow a larger message size for a single policy and keep the default limit of 2,5MB for the rest of the Gateway?
Thank you!
Regards Stefan :)
Original Message:
Sent: May 11, 2015 12:23 PM
From: Doyle Reece
Subject: Re: How do we determine Maximum Message Size supported by the Gateway?
Yeah, you can tweak the settings to handle pretty much any size, as long as the host has the resources to handle it. A few notes:
- The cluster wide property io.xmlPartMaxBytes is the first layer of restriction and is defaulted to 2.5 mb.
- In the listener itself, you can override this in the 'Advanced' tab ( for the Request )
- in the route(http) assertion, you can override the response max size
- using the 'Message Size Limit' assertion, you can specify either the Request,Response,custom contexts and enforce a size limit here as well.
hope this helps James,
thanks,
Doyle