[opencms-dev] CmsDbSqlException?

[Jonathan Woods]

Yes, it looks like a pool management problem.  I'm no expert in this area,
but I don't think maxActive would do it. 

Before I send you on a wild goose chase, I suppose there's nothing odd about
the property "Hidden" you're defining on resources?  First thing to try
might be to remove the property definition (use
Workplace/Administration/Content Tools) then re-apply it - the old 'turn it
off then turn it back on' trick!  This would affect all resources, so it
depends how sensitive your content data is at the moment.

Failing that, I found one other reference from a while back, though this
doesn't give you much:

http://mail.opencms.org/pipermail/opencms-dev/2005q1/015702.html

The next thing I'd try is looking at config parameters available to DBCP
(the pooling library which OpenCms is using here).  The DBCP project is at

http://jakarta.apache.org/commons/dbcp/

and I presume many if not all of the config parameters would be honoured if
you put them in opencms.properties.  If they're not honoured directly in the
form DBCP expects them, you could try digging around in OpenCms source code
to find out how it uses them.

But hopefully another reader has met the problem before and sorted it out...

Jon

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Dong, Roland
Sent: 07 June 2006 16:58
To: opencms-dev at opencms.org
Subject: [opencms-dev] CmsDbSqlException?

Jon,

Thanks for your reply.  We use Oracle. I don't think we have altered anyting
in opencms.properties.  

I noticed the following configuration:

# the maximum number of objects that can be borrowed from the pool
db.pool.default.maxActive=25

# the maximum amount of time before throwing an exception when the pool is
exhausted db.pool.default.maxWait=2000

# the maximum number of objects that can sit idled in the pool
db.pool.default.maxIdle=10


And statement pooling:

# Configuration for statement pooling
########################################################################
#########
db.statements.default.pooling=true
db.statements.default.maxActive=200
db.statements.default.maxWait=2000
db.statements.default.maxIdle=100
db.statements.default.whenExhaustedAction=block

So you think it si connection pooling problems.  Change maxActive?

Thanks so much.

Roland

_______________________________________________
This mail is sent to you from the opencms-dev mailing list To change your
list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev