Oracle Service Bus, Request Entity Too Large

In the osb we use business services (http transport + wsdl) to call our composites on the soa suite.
In a few situations the routing in the osb fail with the next error

<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
	<con:errorCode>BEA-380000</con:errorCode>
	<con:reason>Request Entity Too Large</con:reason>
	<con:location>
		<con:node>RouteNodeLeesDeclaratieCompleet</con:node>
		<con:path>response-pipeline</con:path>
	</con:location>
</con:fault>

Looking in the list of instances in the soa suite we see the instances over there just complete in a valid way but still the routing in the osb fails.

Solution

  • Go to the configuration of the business service
  • Go to the HTTP Transport tab
  • Disable “Use Chunked Streaming Mode”

See also this blog for some extra explanation

Share this Post:
Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

3 Responses to “Oracle Service Bus, Request Entity Too Large”

commenter

OSB or SOA Suite(BPEL), which performs better under heavy load of requests? Any stats on this would be of great help

commenter

Well both are used for different use cases. BPEL should be used for orchestrating processes. If you purely look at the performance aspect, OSB will give you better results. BPEL will store instance data to his dehydration store. OSB is stateless.

Leave a Reply:

Name (required):
Mail (will not be published) (required):
Website:
Comment (required):
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>