Timed out error,anyone could help?

Question

we have met the problem BEA-001131 again and agian recently.the message in the server log shows like this:
Received an exception when closing a cached statement for th BEA-001131 Error JDBC Dec 4, 2006 9:43:35 AM GMT+08:
e pool "billTest": java.sql.SQLException: Io exception: Conn
ection timed out.>
and there's no stackTrace in either the server log or our web application log.
after this error occures,all querys to the database fails.
we use Oracle and Weblogic8.1 SP4,and i know there'some hosts in poor networks cause this error.so modified the "Complete Message Timeout" and "Idle Connection Timeout" in Protocol->General to a really big enough number,180s,and also the "Duration" in Http settings.but the error still occures.
here's our connection pool and data source settings:
<JDBCConnectionPool CapacityIncrement="1"
ConnLeakProfilingEnabled="true"
DriverName="oracle.jdbc.OracleDriver" InitialCapacity="30"
MaxCapacity="200" Name="billTest"
PasswordEncrypted="XXXXXXXXXXXXXXXXXXX"
Properties="user=UserXXX" Targets="ServerXXX"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@xxx.xxx.xxx.xxx:xxx:sid"/>
<JDBCTxDataSource JNDIName="DS" Name="DS"
PoolName="billTest" Targets="ServerXXX"/>
any advice will be helpful,thanks a lot.

Answer 1

Han Bo wrote:
we have met the problem BEA-001131 again and agian recently.the message in the server log shows like this:
Received an exception when closing a cached statement for th BEA-001131 Error JDBC Dec 4, 2006 9:43:35 AM GMT+08:
e pool "billTest": java.sql.SQLException: Io exception: Conn
ection timed out.>
and there's no stackTrace in either the server log or our web application log.
after this error occures,all querys to the database fails.
we use Oracle and Weblogic8.1 SP4,and i know there'some hosts in poor networks cause this error.so modified the "Complete Message Timeout" and "Idle Connection Timeout" in Protocol->General to a really big enough number,180s,and also the "Duration" in Http settings.but the error still occures.
here's our connection pool and data source settings:
<JDBCConnectionPool CapacityIncrement="1"
ConnLeakProfilingEnabled="true"
DriverName="oracle.jdbc.OracleDriver" InitialCapacity="30"
MaxCapacity="200" Name="billTest"
PasswordEncrypted="XXXXXXXXXXXXXXXXXXX"
Properties="user=UserXXX" Targets="ServerXXX"
TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@xxx.xxx.xxx.xxx:xxx:sid"/>
<JDBCTxDataSource JNDIName="DS" Name="DS"
PoolName="billTest" Targets="ServerXXX"/>
any advice will be helpful,thanks a lot.Hi. You need to turn on TestConnectionsOnReserve in the pool,
so it will test connections before giving them to you, and
replace bad ones.
Joe