2011 Storage - JDBC Error

Question

An error occurred in our logs when we used PageMetaFactory to get meta information on the page:

Unable to release connection

Due to some digging, is this apparently caused by an application trying to use a connection from the connection pool that was inactive after a timeout?

This made me think of a section in the repository configuration:

<Storage Type="persistence" Id="defaultdb" dialect="MSSQL" Class="com.tridion.storage.persistence.JPADAOFactory"> <Pool Type="jdbc" Size="5" MonitorInterval="60" IdleTimeout="120" CheckoutTimeout="120" /> <DataSource Class="com.microsoft.sqlserver.jdbc.SQLServerDataSource"> <Property Name="serverName" Value="COAIPDELIVDBP01" /> <Property Name="portNumber" Value="xxx" /> <Property Name="databaseName" Value="Tridion_Broker" /> <Property Name="user" Value="xxxx" /> <Property Name="password" Value="xxx" /> </DataSource> </Storage> 

I never had any reason to change them outside the default and I wondered if these settings played part of the error?

EDIT

Added full node storage. We run:

• SQL Server 2008 R2 64bit
• Windows Server 2008 R2
• 64-bit JRE 1.6.0 64bit

Greetings

Answer 1

Typically, this error occurs because the IdleTimeout in your storage configuration is larger than your IdleTimeout database. What is an IdleTimeout? This is a timeout on idle connections. If Tridion uses a connection that has been idle in the connection pool outside the database timeout period, an exception is thrown. So, in your case, the explanation may be that Tridion is trying to use a database connection that was close to the database server because it has been idle for too long. To make sure this does not happen in the future, find out what WaitTime is defined at your database level and set IdleTimeout to a smaller or smaller value (note that in the storage configuration this timeout is defined in seconds).

Hope this helps.

Regards, Daniel.