My Oracle Support Banner

After Upgrade, in 12.2.1.4 service callout timeout error(OSB-380002) no longer being reported in pipeline instead OSB-382502 is reported (Doc ID 2711974.1)

Last updated on SEPTEMBER 17, 2020

Applies to:

Oracle Service Bus - Version 12.2.1.4.0 to 12.2.1.4.0
Information in this document applies to any platform.

Symptoms

On : 12.2.1.4.0 version, OSB Core Functionality

ACTUAL BEHAVIOR
---------------

After upgrading to 12.2.1.4 when Service Callout gets a SocketTimeoutException, the returned error code is OSB-380002; however, User's Service Error Handler gets a generic OSB-382502 errorCode instead.

EXPECTED BEHAVIOR
-----------------------

Should return error code as below.

OSB-380002
connect timed out

 

In 12.2.1.4 get below error code

OSB-382502
OSB Service Callout action received an error response

Instead of below what was seen in 12.2.1.3.0

OSB-380002
connect timed out

 

 


 Checking the error stack for the SocketTimeoutException received in customer logs could see the flow as below.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.