OSB 10.3 not Timing Out if Service Using HTTP Transport is not Available
(Doc ID 859261.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Service Bus - Version 2.0 and later
Information in this document applies to any platform.
***Checked for relevance on 12-May-2014***
You have a OSB business service with HTTP transport. The external service to which the business service connects is completely down and does not respond to a TCP connect.
1. Timeout on the business set to 10 seconds.
2. OSB tries to call the external service but it is not even able to connect.
3. OSB seems to wait for a long time and does not timeout after the defined 10 seconds.
This scenario does not seem to work as expected. Instead what happens is, we do not get a timeout, the request only times out after the socket times out after about 3 minutes.
The log files are showing the following messages:
<Error> <OSB Kernel> <BEA-398204> < [OSB Tracing] Internal Error while tracing message null>
The SOAP response is:
BEA-380002: Tried all: '1' addresses, but could not connect over HTTP to server:
'xxx.xxx.xxx.xxx', port: 'xxx'
Tried all: '1' addresses, but could not connect over HTTP to server: 'xxx.xxx.xxx.xxx', port: 'xxx'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document