RETRY (and RETRY_DIS) Functionality
(Doc ID 2274476.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.
The following error is seen in JNEP diag file.
"org.apache.axis2.AxisFault: Transport error: 408 Error: Request Timeout"
Customer has an ASDL retry mechanism implemented for below scenarios/cases.
- SocketException: Broken pipe (errno:32)
- java.net.SocketException:Connection reset
- Read timed out.
Now, if there is already a RETRY mechanism at the network level, why is one needed at the ASDL level for the case mentioned.
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