http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2190
*** shadow/2190 Thu Jul 19 10:36:12 2001
--- shadow/2190.tmp.7357 Thu Jul 19 11:15:30 2001
***************
*** 2,9 ****
| unable to use connection pooling in esql |
+----------------------------------------------------------------------------+
| Bug #: 2190 Product: Cocoon 2 |
! | Status: NEW Version: 2.0alpha CVS |
! | Resolution: Platform: PC |
| Severity: Major OS/Version: Linux |
| Priority: Other Component: core |
+----------------------------------------------------------------------------+
--- 2,9 ----
| unable to use connection pooling in esql |
+----------------------------------------------------------------------------+
| Bug #: 2190 Product: Cocoon 2 |
! | Status: RESOLVED Version: 2.0alpha CVS |
! | Resolution: WORKSFORME Platform: PC |
| Severity: Major OS/Version: Linux |
| Priority: Other Component: core |
+----------------------------------------------------------------------------+
***************
*** 78,80 ****
--- 78,102 ----
------- Additional Comments From [EMAIL PROTECTED] 2001-07-19 10:36 -------
This problem isn't appearing when the database driver is set to HSQL.
+
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-07-19 11:15 -------
+ Check the very beginning of your cocoon.log file:
+ If no Connections could be established then the pool cannot
+ be initialized.
+
+ The most common reason for this is not placing the driver class in
+ the list of classes to load on initialization ("load-class" initial
+ parameter in WEB-INF/web.xml).
+
+ Please check you web.xml file for the following entry:
+
+ <init-param>
+ <param-name>load-class</param-name>
+ <param-value>
+ <!-- list of comma or whitespace delimited fully qualified
+ class names to load on initialization
+ -->
+ oracle.jdbc.driver.OracleDriver
+ </param-value>
+ </init-param>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
