WebLogic Connection Timeout Problem solution

WebLogic The connection pool configuration database automatically after the Disconnect setting :
Go to a Connection pool configuration page, go to the Connections page, and click Show on advanced options to display advanced options.

Specify test frequency and enable test reserved connections, test-created connections, and test-freed connections.

Testing frequency (Test Frequency): 60 seconds

The number of seconds between automatic database connection tests (0-32-bit positive integers). The test failed connection will be closed and reopened to re-establish a valid physical database connection. (You must specify the test table name below.) )

The number of seconds (between 0 and a positive 32-bit integer) between automatic database connection tests. Connections that fail the test are closed and reopened to re-establish a valid physical database connection. (You must specify a Test Table Name below.)

Test reserved connections (test Reserved connections)

Specifies whether WebLogic Server tests the connection before it is provided to the client. (You must specify the test table name below.) )

Specifies whether WebLogic Server tests a connection before it to the client. (You must specify a Test Table Name below.)

Test the created connection (test Created connections)

Specifies whether WebLogic Server tests the connection after it has been created and adds the connection to the list of available connections in the buffer pool. (You must specify a test table name.) )

Specifies whether WebLogic Server tests a connection after creating it but before it to the list of adding AVA Ilable in the pool. (You must specify a Test Table Name.)

Test the Freed connection (test released connections)

Specifies whether WebLogic Server tests the connection before returning it to the JDBC connection buffer pool. (You must specify a test table name.) )

Specifies whether WebLogic Server tests a connection before returning it to this JDBC connection pool. (You must specify a Test Table Name.)

Connection retention timeout (Connection reserve Timeout): set to 30 seconds

The number of seconds (-1-32-bit positive integers) before the call timeout for a buffer pool connection is preserved. If set to-1, the call never times out.

The number of seconds (between-1 and a positive 32-bit integer) after which a call to reserve a connection from the pool would timeout. When set to 0, a call would never timeout. When set To-1, a call to'll timeout immediately

Retry the creation of the connection frequency (Connection creation retry Frequency): Set to 30 seconds interval seconds (0-32-bit positive integers) that attempt to establish a connection to the database. Applies to the connection buffer pool that is created when the server is started when the database is not available.

The number of seconds (between 0 and a positive 32-bit integer) between attempts to establish connections to the database. Applies to connection pools created at server startup, the database is unavailable.

Passivation Connection Timeout (Inactive Connection Timeout):

The number of inactive seconds on a reserved connection (between 0 and a positive 32-bit integer) before WebLogic Server R Eclaims the connection and releases it back into the connection pool.

The server requests a reconsideration connection and retains the passivation time before returning to the connection pool

Test Table Name:

Oracle's connection Chime that the SQL SELECT 1 from dual,sybase database can be populated with a few records of configuration table names such as Sys_code.

The name of the database table to use when testing physical database connections. This are required when you specify a test Frequency and enable test Reserved connections, test Created connections, a nd Test released connections.

The previous article describes one of the setup methods, and if you set the timeout for the WebLogic session to control the WebLogic connection timeout problem:

1 web.xml
Sets the elements in the Web application descriptor Web.xml. This value is in minutes
Units, and overwrite the Timeoutsecs attribute in Weblogic.xml

54

This example indicates that the session will expire in 54 minutes
When set to-2, indicates that the set in Weblogic.xml will be used
Timeoutsecs this property value.
When set to-1, the session will never expire, ignoring the
The value of the Timeoutsecs property set in Weblogic.xml.
This property value can be set by using the console console

2 Weblogic.xml

That sets the elements of the WebLogic-specific deployment descriptor weblogic.xml.
Timeoutsecs property. This value is measured in seconds

Timeoutsecs 3600

The default value is 3,600 seconds

Control in 3,jsp

Session.setmaxinactiveinterval (7200);

The session is the default object, which can be referenced directly, in per second s

Control in 4,servlet

HttpSession session = Request.getsession ();

Session.setmaxinactiveinterval (7200);

Per second S

In Weblgoic console: Xxdomain->servers->xxserver->protocols->http has a configuration about post timeout, but this parameter generally uses the default value

Typically through Services–>jdbc–>connection pools–>myconnection (the connection pool name you create)-->configration–>connections Inactive Connection Timeout This parameter to set, the default is 0, indicating that the connection time is infinitely long. You can set a time value that connects over this time value, and it forces the connection back into the connection pool.

completemessagetimeout= "Idlec"
Listenaddress= "" "listenport=" 7001 "name=" MyServer "
Nativeioenabled= "true" reliabledeliverypolicy= "Rmdefaultpolicy"
serverversion= "8.1.4.0" >
Whether to idleconnectiontimeout parameters

Look at the number of inactive Connection timeout and Connection Reserve timeout in the advanced options in the connection pool, and try to make these two larger.