Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

connection timeout in SOA composite.xml not working as expected

641097May 15 2012
Hi All

We are trying to invoke two webservices from flow activity in parallel in a SOA Composite. Both invokes need to have a connection time out of 5 seconds and read time out of 25 seconds (See extract of composite.xml below).

<reference name="sgdg"
ui:wsdlLocation="sgdfgd.wsdl">
<interface.wsdl interface="asdfasdfasdfasdf"/>
<binding.ws port="fadsfsaffsd"
location="asdADSDa?wsdl"
soapVersion="1.1">

<property name="oracle.webservices.httpConnTimeout" type="xs:integer"
many="false" override="may">5000</property>
<property name="oracle.webservices.httpReadTimeout" type="xs:integer"
many="false" override="may">25000</property>
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
</binding.ws>
</reference>
<reference name="dssadff_OrderService"
ui:wsdlLocation="sdfasdfs.wsdl">
<interface.wsdl interface="affadfs"/>
<binding.ws port="asfdsfasfsdffasfd"
location="dfasdfasfasdf?wsdl"
soapVersion="1.1">

<property name="oracle.webservices.httpConnTimeout" type="xs:integer"
many="false" override="may">5000</property>
<property name="oracle.webservices.httpReadTimeout" type="xs:integer"
many="false" override="may">25000</property>
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
</binding.ws>
</reference>

After setting these values, the service still hangs for 300 seconds (coz one of the endpoints is down and not reachable). The oracle.webservices.httpConnTimeout property is not working and the fault comes after 300 seconds. The calling application does not wait this long. Please let us know when are we doing wrong? Here is some more info for you to work with:

1) This composite is invoked via Direct Binding and is called from the OSB via soa-direct protocol, the OSB proxy service is further exposed to a system (SOAP\HTTP) which wants a fault or response in 30 seconds.
2) Both the web service references are invoked within a flow activity in parallel (does timeout not work with the flow activity?).
3) SyncMaxWaitTime is 45 seconds, BPEL EJB transaction Time out is 300 seconds and JTA is 360 seconds.

Please help resolve this issue. Thanks
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 12 2012
Added on May 15 2012
0 comments
1,578 views