I am using OJB with HSQL and the following connection descriptor in a
Struts based web application. I very frequently see a message saying
that the connection was closed and destroy object was called. It
appears as if the connection pooling is not working as it should. Am I
missing a setting - or is this a known issue. I could add
whenExhaustedAction=2 to work around it but want to know the root cause.
Thanks in advance.
Raghavan
<jdbc-connection-descriptor
jcd-alias="default"
default-connection="true"
platform="Hsqldb"
jdbc-level="3.0"
driver="org.hsqldb.jdbcDriver"
protocol="jdbc"
subprotocol="hsqldb:hsql"
dbalias="//localhost"
username="sa"
password=""
eager-release="false"
batch-mode="false"
useAutoCommit="0"
ignoreAutoCommitExceptions="false"
>
<connection-pool maxActive="21" validationQuery="select count(*)
from role"/>
<sequence-manager
className="org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImp
l">
<attribute attribute-name="autoNaming" attribute-value="true"/>
<attribute attribute-name="grabSize" attribute-value="20"/>
<attribute attribute-name="globalSequenceId"
attribute-value="false"/>
<attribute attribute-name="globalSequenceStart"
attribute-value="10000"/>
</sequence-manager>
</jdbc-connection-descriptor>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
