Comparing oracle.net.CONNECT_TIMEOUT and JDBC statement-timeout values for SOA 11g default datasources.

Comparing oracle.net.CONNECT_TIMEOUT and JDBC statement-timeout values for SOA 11g default datasources.

Default Data Sources that can be checked in Weblogic console:

SOA
SOA Local TX
EDN
EDN Local TX
mds-soa
mds-owsm

Under $DOMAIN_HOME>/config/jdbc

Check the specific configuration files:

mds-soa-jdbc.xml
mds-owsm-jdbc.xml
SOADataSource-jdbc.xml
SOALocalTxDataSource-jdbc.xml
EDNDataSource-jdbc.xml
EDNLocalTxDataSource-jdbc.xml


In each file look for entries like below:

<property>
        <name>oracle.net.CONNECT_TIMEOUT</name>
        <value>10000</value>
</property>

and

<statement-timeout>60</statement-timeout>

It is recommended to set both the properties and that statement-timeout value exceeds that of CONNECT_TIMEOUT. Both the properties can be set in Weblogic Console in Data Source configuration area.

Setting these properties ensures you do not end up with stuck threads in runtime or a hung server requiring restart.