cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "neil" <>
Subject RE: avalon.excalibur ping of oracle fails
Date Wed, 16 Oct 2002 01:04:57 GMT
In cocoon.xconf, the oradb attribute in <pool-controller oradb="true" is apparently no longer
Instead, a child element allows you to specify the sql to be used to ping the database connection
like this:
  <pool-controller max="5" min="2">
    <keep-alive disable="false">select 1 from dual</keep-alive>
If you don't specify <keep-alive> it defaults to "select 1", which seems to be OK for
except Oracle.

-----Original Message-----
From: neil []
Sent: Tuesday, 10 September 2002 3:23 PM
To: Cocoon-Users (E-mail)
Subject: avalon.excalibur ping of oracle fails

Has anyone using oracle already solved this one?

Although my app works OK, I'm getting debug messages (shown below) indicating that the database
"ping" fails
so cocoon is dicarding the connection and creating a new one.
I guess its going slower than it could due to this.

I do have
    <jdbc ...>
      <pool-controller oradb="true" ...
in my cocoon.xconf, but this doesn't seem to be finding its way into
org.apache.avalon.excalibur.datasource.AbstractJdbcConnection where it executes the query
to ping the database (a different query for oracle than for other rdbms's).

My cocoon is a snapshot of the cocoon_2_0_3_branch taken on 2002-08-16 and
has WEB-INF/lib/avalon-excalibur-vm14-20020705.jar.

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message