SOA 11g Deployments are Retried when Connection is Reset
(Doc ID 1310499.1)
Last updated on AUGUST 31, 2018
Applies to:Oracle SOA Suite - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When deploying through Scripts we are calling the soaDeployComposite.py script and the method sca_deployComposite.
This method does a HTTP Post to soa-infra/deployer servlet using HTTPConnection class in oracle.http_client_11.1.1.jar. In this class there is a method called sendRequest, which has the code shown below (nb: this code is referenced from the jar file):
int try_count = 3;
while (try_count-- > 0)
if (resp != null)
resp.timeout = Timeouts.zero; break;
Since ADC (Application Delivery Controller Load Balancer) timeout is 5 minutes, when the deployments goes beyond 5 minutes it gets a connection reset which in turn the response is null, so it's retrying the request for 3 times. It's hard coded in the jar class. User has no control over it. By increasing the ADC timeout to 15 mins which will only postpone the problem.
User needs this to be configurable, instead of hard coding it in the jar file to 3 times. User doesn't want the infrastructure to do retires.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|