tag:blogger.com,1999:blog-3102468434043486639.post6712607173020491270..comments2024-03-17T23:30:49.469-07:00Comments on Roy's musings: Gotchas with DBCPRoyhttp://www.blogger.com/profile/00633074227808113222noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3102468434043486639.post-15959050276376827332017-05-26T04:28:16.511-07:002017-05-26T04:28:16.511-07:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/14136224845945232818noreply@blogger.comtag:blogger.com,1999:blog-3102468434043486639.post-60786573731468731552016-11-05T00:49:21.655-07:002016-11-05T00:49:21.655-07:00There is indeed a lot help for the students out th...There is indeed a lot help for the students out there and hopefully the instances will bring students around all those stories which would even help them. comment plugin wordpresshttp://plugins.wpservice.org/best-wordpress-comment-plugins/noreply@blogger.comtag:blogger.com,1999:blog-3102468434043486639.post-8689014559048764032015-03-20T04:34:47.926-07:002015-03-20T04:34:47.926-07:00Nice post
I have a problem with DBCP
start everyth...Nice post<br />I have a problem with DBCP<br />start everything works correctly but after the session fermture forsaken I have a type error<br /><br />Caused by: java.sql.SQLException: Connection org.postgresql.jdbc3.Jdbc3Connection@20941296 is closed<br /><br />my parammetre <br /><br />"hibernate.dbcp.validationQuery" = select 1<br />"hibernate.dbcp.initialSize"=10<br />"hibernate.dbcp.maxActive"=100<br />"hibernate.dbcp.maxIdle"=80<br />"hibernate.dbcp.minIdle"=10<br />"hibernate.dbcp.maxWait"=40000<br />"hibernate.dbcp.testOnReturn"=true<br />"hibernate.dbcp.testOnBorrow"=true<br />"hibernate.dbcp.testWhileIdle"=true<br />"hibernate.dbcp.timeBetweenEvictionRunsMillis"=420000<br />"hibernate.dbcp.minEvictableIdleTimeMillis"=300000<br />"hibernate.dbcp.validationInterval"=25000><br />"hibernate.dbcp.removeAbandoned"=true<br />"hibernate.dbcp.removeAbandonedTimeout"=50<br />"hibernate.dbcp.logAbandoned"=true<br />"hibernate.dbcp.poolPreparedStatements"=false<br /><br /><br />thanks for your helpAnonymoushttps://www.blogger.com/profile/10072700687733423030noreply@blogger.comtag:blogger.com,1999:blog-3102468434043486639.post-4281430014925141622009-12-08T21:30:31.324-08:002009-12-08T21:30:31.324-08:00Nice post! You saved my day.Nice post! You saved my day.Unknownhttps://www.blogger.com/profile/11263068643007736079noreply@blogger.comtag:blogger.com,1999:blog-3102468434043486639.post-10281838807537409582009-12-03T12:00:10.003-08:002009-12-03T12:00:10.003-08:00Connection pooling in Java just seems unnecessaril...Connection pooling in Java just seems unnecessarily complicated, IMO. BoneCP looks to be a nice solution.chetanhttps://www.blogger.com/profile/17623169727903528482noreply@blogger.comtag:blogger.com,1999:blog-3102468434043486639.post-49383773882025216922009-11-11T06:30:53.501-08:002009-11-11T06:30:53.501-08:00DBCP's synchronized() mania is one reason why ...DBCP's synchronized() mania is one reason why I wrote BoneCP (http://jolbox.com) -- the benchmark section shows that the end result is a connection pool that's faster than both C3P0 and DBCP.<br /><br />IMHO testOnBorrow is useless for a connection might drop the very next moment a connection is tested.woghttps://www.blogger.com/profile/03435404521669261086noreply@blogger.com