BEA Weblogic AS 9.2 close pool connections - messages BEA-001128 in logs

Question

Hello,
We have problems with BEA Weblogic AS 9.2 SP3. From time to time servers stop responding and seem to be stuck.
In logs there are plenty of messages like this:
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729759> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729759> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729759> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729774> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729774> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729774> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729774> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:49 PM CEST> <Info> <JDBC> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245157729774> <BEA-001128> <Connection for pool "GoD-PRD" closed.>
####<Jun 16, 2009 3:08:50 PM CEST> <Info> <Common> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-4A32C18C5F55D8E4A47E> <> <1245157730603> <BEA-000628> <Created "5" resources for pool "GoD-PRD", out of which "5" are available and "0" are unavailable.>
####<Jun 16, 2009 3:12:13 PM CEST> <Info> <Common> <SRV-WLS3> <PRD-J> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-637BC18C5F55D8E4A47E> <> <1245157933416> <BEA-000628> <Created "5" resources for pool "GoD-PRD", out of which "5" are available and "0" are unavailable.>
What exactly this message mean? Does it show some invalid behavior in application or it is just standard notice message?
What should be behavior of app. server when transaction is timed out on database and closed there? We have timeout for one operation on Oracle set on 10 minutes. Maybe there is a connection between the problems?
Thanks allot!
Miroslav

Answer 1

Test is not enabled. Network should be stable all time - part of one switch.
Here is a configuration for no-TX source:
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>GoD-PRD</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@db_server:1521:cml</url>
<driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name>
<properties>
<property>
<name>user</name>
<value>our_user</value>
</property>
</properties>
<password-encrypted>xxxxxx</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>100</max-capacity>
<capacity-increment>5</capacity-increment>
<test-connections-on-reserve>false</test-connections-on-reserve>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>idit.jdbc.IDITDS</jndi-name>
<global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
Edited by: myroch on 14.7.2009 4:48