Last updated on OCTOBER 18, 2016
Applies to:Oracle Service Bus - Version 10.3 and later
Information in this document applies to any platform.
OSB 10.3 is sending HTTP 1.1 request to the end service. They noticed sometimes that the header is getting passed to the end service but the body is not contaning any content which causes OSB 500 error.
This can happen when sending a WebService request using HTTP 1.1 and keep alive to a backend system, where the keep alive timeout is set lower than on the client side. If the keep alive timeout fires on the backend system, the connection gets closed with a reset. Then client is sending its message again without the
body. It can also happen when keep-alive is disabled on the backend system
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms