Customize Synchronous Timeout

Problem Statement
While coding, we do come across a challenging situation where one service demands a different timeout value as compared to the global timeout value. Consider a scenario where 1 out of 20 services needs a different value as compared to the global synchronous max wait time value.

One cannot amend the global synchronous timeout value as it impacts the rest of the services.

Solution
SOA services have provided us with httpReadTimeout and local optimization properties, which gives the developers the liberty to customize the synchronous timeout value.

The above properties needs to mention within the composite.xml under the reference name, which has a strict clock to follow.

Usage in composite.xml:
<property name=”oracle.webservices.httpReadTimeout” type=”xs:string” many=”false” override=”may”>70000</property>

<property name=”oracle.webservices.local.optimization” type=”xs:boolean” many=”false” override=”may”>false</property>

NOTE:

1. Please use both the above properties to customize the synchronous timeout value
2. Unit for value 70000 is milliseconds, so please be mindful to convert your synchronous timeout value into milliseconds