Reputation: 131
I have a mule flow that uses the http:request and this flow is running multiple requests through it at the same time (synchronously). On only a few of the request I will receive the following error:
HTTP packet header is too large (java.lang.IllegalStateException)
The problem here is that the service I am sending the request to receives these like normal and then it blows up in mule so I don't get the correct response that I am looking for.
So in the other system it looks like the call was successful, but on my end it is a failure. I am fairly new to mule so go easy on me lol!
Any and all help would be greatly appreciated.
Upvotes: 0
Views: 1904
Reputation: 33413
This is not a Mule error message. It looks like people report this issue with Grizzly.
I guess Mule sends a header that the server you're calling finds too big. I bet it's the serialized session. If you are using the http
transport, this can be disabled like this:
<http:connector name="NoSessionConnector">
<service-overrides sessionHandler="org.mule.session.NullSessionHandler"/>
</http:connector>
If you are using the new HTTP connector, well, someone else will have to tell you how to disable it...
EDIT: Adding comment from Anirban.
With the new HTTP connector, use:
<remove-property propertyName="MULE_SESSION" />
to remove the massive session header.
Upvotes: 1