cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: NEW FAQ ENTRY--Re: [Bug 2190] - unable to use connection pooling in esql
Date Fri, 20 Jul 2001 15:35:07 GMT

Berin Loritsch a écrit :
> Question:
> When I try to use the Connection pooling code, I get the following
> exception:
> Could not get the datasource java.sql.SQLException: You cannot
> get a Poolable before the pool is initialized
> What's going on?
> Answer:
> The most common reason for this exception is that the driver was not loaded.
> Cocoon uses an initial parameter in the "web.xml" file to automatically load
> classes on startup.  This way, the class is loaded only once and the
> server's
> time is spent doing more productive things.  Make sure the following entry
> is in your "web.xml" file:
> <init-param>
>   <param-name>load-class</param-name>
>   <param-value>
>     <!-- comma or whitespace separated list of fully qualified class names
>         to load on startup.
>     -->
>     oracle.jdbc.driver.OracleDriver
>   </param-value>
> </init-param>
> If the class is loaded correctly, and you are still getting this error,
> then there
> is probably an error in your connection information.  The SQLException
> above is thrown when there are no open connections to the database.

Even if placing JDBC drivers in the load-class param can be justified
from a design point of view (it's loaded only once, it's a deployment
parameter, etc), it appears that it is confusing users. This is mainly
because nearly all tools that rely on a JDBC connection (including C1)
ask for the JDBC url and driver class at the same time or place.

What about allowing to optionally specify the driver class name in the
datasource configuration ?

Sylvain Wallez
Anyware Technologies -

To unsubscribe, e-mail:
For additional commands, email:

View raw message