In our development env, we have a single Tridion 2013 installation, with only 2 threads for rendering and 2 threads for deploying configured on the CMS server. Broker storage is a MSSQL database. Our single Deployer instance runs as a Websphere 8.5 application (JDK1.7) on the same server as several other Java applications that all depend on the Tridion 2013 storage. These applications are NOT running at the moment. The Deployer uses the following connection-related settings:

If we republish the failed page(s) separately at some later moment, they publish succesfully???

In our development env, we have a single Tridion 2013 installation, with only 2 threads for rendering and 2 threads for deploying configured. Storage is a SQL Server 2008R2 database. Our Deployer runs as a Websphere 8.5 application (JDK1.7). 
The Deployer uses the following connection-related settings:

If we republish the failed page(s) separately at some later moment, they publish succesfully? If anyone else is using SQL Server 2008R2, please let me know the connection properties/pooling used to connect to the DB so we can troubleshoot.