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:

• connP.agedTimeout=0
• connP.connectionTimeout=180
• connP.maxConnections=10
• connP.minConnections=0
• connP.purgePolicy=EntirePool
• connP.reapTime=180
• connP.unusedTimeout=1800
• prop.syncQueryTimeoutWithTransactionTimeout=
• prop.webSphereDefaultIsolationLevel=
• statementCacheSize=20

When we publish some tens of pages, we randomly get LockAcquisitionException errors in our deployer/broker log:

[DEBUG] 2015-02-10 14:16:55,232 com.tridion.util.xml.XMLParser:98     - Parsing XML with encoding null
[ INFO] 2015-02-10 14:16:55,234 com.tridion.deployer.phases.DeployPipelineExecutor:97     - Executing deployment phase: Deployment Processing Phase for transaction: tcm:0-1359110-66560
[ INFO] 2015-02-10 14:16:55,237 com.tridion.deployer.phases.ProcessingPhase:65     - Starting executing of phase: PRE_PROCESSING for transaction: tcm:0-1359110-66560
[DEBUG] 2015-02-10 14:16:55,237 com.tridion.deployer.workers.ProcessorWorker:54     - Starting processors for phase: pre-processing
[ INFO] 2015-02-10 14:16:55,237 com.tridion.deployer.ProcessorFactory:105     - Creating processors for phase: pre-processing
[DEBUG] 2015-02-10 14:16:55,237 com.tridion.deployer.workers.ProcessorWorker:80     - Processors finished for phase: pre-processing
[ INFO] 2015-02-10 14:16:55,238 com.tridion.deployer.phases.ProcessingPhase:70     - Starting executing of phase: PROCESSING for transaction: tcm:0-1359110-66560
[DEBUG] 2015-02-10 14:16:55,238 com.tridion.deployer.workers.ProcessorWorker:54     - Starting processors for phase: processing
[ INFO] 2015-02-10 14:16:55,238 com.tridion.deployer.ProcessorFactory:105     - Creating processors for phase: processing
[ INFO] 2015-02-10 14:16:55,240 com.tridion.deployer.Module:53     - No TransformProcessor configured, will not transform files before deployment for module com.tridion.deployer.modules.SchemaDeploy
[ WARN] 2015-02-10 14:16:55,242 org.hibernate.engine.jdbc.spi.SqlExceptionHelper:143     - SQL Error: 1205, SQLState: 40001
[ERROR] 2015-02-10 14:16:55,242 org.hibernate.engine.jdbc.spi.SqlExceptionHelper:144     - Transaction (Process ID 69) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
[ WARN] 2015-02-10 14:16:55,243 com.tridion.deployer.phases.PreCommitPhase:127     - Failed to Prepare: tcm:0-1359100-66560 error: org.hibernate.exception.LockAcquisitionException: Transaction (Process ID 69) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
[ INFO] 2015-02-10 14:16:55,243 com.tridion.storage.StorageManagerFactory:466     - Rolling back storage transaction: tcm:0-1359100-66560

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