AutoCommit throwing NullPointerException

Ask around here!

AutoCommit throwing NullPointerException

Postby Dharma » Fri Mar 09, 2012 5:29 am

Hi,

i have configured the BoneCp inside my quartz scheduler with the following parameters
partitionCount=2
maxConnectionsPerPartition=25
minConnectionsPerPartition=25
disableConnectionTracking=true
closeConnectionWatch=false
poolStrategy=CACHED

My quartz is configured with 20 threads. when starting, bonecp gives warning like
"[WorkerThread-15] WARN com.jolbox.bonecp.CachedConnectionStrategy.stealExistingAllocations.154 - Cached strategy chosen, but more threads are requesting a connection than are configured. Switching permanently to default strategy."

is there anything i can do with the configuration to use CachedConnectionStrategy instead of DEFAULT?

while executing the jobs, i got NullPointerException for setting the autocommit property after getting the connection from pool.

java.lang.NullPointerException
at com.jolbox.bonecp.ConnectionHandle.setAutoCommit(ConnectionHandle.java:1316)
at com.report.utilities.ConnectionPool.getConnection(ConnectionPool.java:214)

Here is the code to get connection from BoneCp

public Connection getConnection(boolean autoCommit)
{
Connection con = connectionPool.getConnection();
con.setAutoCommit(autoCommit);
return con;
}
Dharma
 
Posts: 2
Joined: Wed Mar 07, 2012 10:53 am

Return to BoneCP - Help, Q&A, Whatever!

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 3 guests