You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Brian P. Millett" <bp...@ec-group.com> on 2002/06/12 19:21:20 UTC
NoValidConnectionException: No valid JdbcConnection class available
Configuration:
Using CATALINA_BASE: /opt2/jakarta-tomcat-4.0.4-b3
Using CATALINA_HOME: /opt2/jakarta-tomcat-4.0.4-b3
Using CATALINA_TMPDIR: /opt2/jakarta-tomcat-4.0.4-b3/temp
Using JAVA_HOME: /usr/j2se
Solaris 8, jdk 1.4, postgresql 7.2, mysql 4.01
>From cocoon.xconf:
<datasources>
<jdbc name="personnel">
<pool-controller max="10" min="5"/>
<auto-commit>true</auto-commit>
<dburl>jdbc:postgresql://localhost:5432/test</dburl>
<user>XXXX</user>
<password>XXXX</password>
</jdbc>
<jdbc name="mobot">
<pool-controller max="10" min="5"/>
<auto-commit>true</auto-commit>
<dburl>jdbc:postgresql://localhost:5432/ids_tropicos</dburl>
<user>XXXX</user>
<password>XXXX</password>
</jdbc>
<jdbc name="tropicos">
<pool-controller max="10" min="5"/>
<auto-commit>true</auto-commit>
<dburl>jdbc:mysql://tropicos:3306/ids_tropicos</dburl>
<user>XXXX</user>
<password>XXXX</password>
</jdbc>
</datasources>
from web.xml
<init-param>
<param-name>load-class</param-name>
<param-value>
<!-- For PostgreSQL Database Driver: -->
org.postgresql.Driver
<!-- For MySQL Database Driver: -->
org.gjt.mm.mysql.Driver
</param-value>
</init-param>
I get this error in my sitemap.log
ERROR (2002-06-12) 12:02.09:800
[sitemap.generator.serverpages](/cocoon/xsp/esql)
HttpProcessor[8080][4]/esql_xsp: Could not get the datasource
org.apache.avalon.excalibur.datasource.NoValidConnectionException: No
valid JdbcConnection class available
at
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:183)
at
org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable(ResourceLimitingPool.java:491)
at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:140)
at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:81)
at
org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimitingPool.java:314)
at
org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:91)
at
org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:131)
at
org.apache.cocoon.www.docs.samples.xsp.esql_xsp.generate(/opt2/jakarta-tomcat-4.0.4-b3/work/Standalone/localhost/cocoon/cocoon-files/org/apache/cocoon/www/docs/samples/xsp/esql_xsp.java:338)
Any ideas other than "use jdk 1.3.1"? Is this a JNDI problem or a JDBC
problem?
Thanks.
--
Brian Millett
Enterprise Consulting Group "Shifts in paradigms
(314) 205-9030 often cause nose bleeds."
bpm@ec-group.com Greg Glenn
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: NoValidConnectionException: No valid JdbcConnection class
available
Posted by "Brian P. Millett" <bp...@ec-group.com>.
On Wed, 2002-06-12 at 13:29, Gerhard Hipfinger wrote:
> Hi!
>
> I use the current cvs snapshot, and it is working with mm.mysql jdbc
> driver and jdk 1.4. It seems the new excalibur version is already in
> 2.1-dev.
Thanks, that did it. Much easier compiling cocoon-2.1-dev than the
Excalibur src.
--
Brian Millett
Enterprise Consulting Group "Shifts in paradigms
(314) 205-9030 often cause nose bleeds."
bpm@ec-group.com Greg Glenn
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: NoValidConnectionException: No valid JdbcConnection class available
Posted by Gerhard Hipfinger <ge...@openforce.at>.
Hi!
I use the current cvs snapshot, and it is working with mm.mysql jdbc
driver and jdk 1.4. It seems the new excalibur version is already in
2.1-dev.
Gerhard
Brian P. Millett wrote:
>Configuration:
>Using CATALINA_BASE: /opt2/jakarta-tomcat-4.0.4-b3
>Using CATALINA_HOME: /opt2/jakarta-tomcat-4.0.4-b3
>Using CATALINA_TMPDIR: /opt2/jakarta-tomcat-4.0.4-b3/temp
>Using JAVA_HOME: /usr/j2se
>
>Solaris 8, jdk 1.4, postgresql 7.2, mysql 4.01
>
>>>From cocoon.xconf:
> <datasources>
> <jdbc name="personnel">
> <pool-controller max="10" min="5"/>
> <auto-commit>true</auto-commit>
> <dburl>jdbc:postgresql://localhost:5432/test</dburl>
> <user>XXXX</user>
> <password>XXXX</password>
> </jdbc>
> <jdbc name="mobot">
> <pool-controller max="10" min="5"/>
> <auto-commit>true</auto-commit>
> <dburl>jdbc:postgresql://localhost:5432/ids_tropicos</dburl>
> <user>XXXX</user>
> <password>XXXX</password>
> </jdbc>
> <jdbc name="tropicos">
> <pool-controller max="10" min="5"/>
> <auto-commit>true</auto-commit>
> <dburl>jdbc:mysql://tropicos:3306/ids_tropicos</dburl>
> <user>XXXX</user>
> <password>XXXX</password>
> </jdbc>
> </datasources>
>
>from web.xml
> <init-param>
> <param-name>load-class</param-name>
> <param-value>
> <!-- For PostgreSQL Database Driver: -->
> org.postgresql.Driver
> <!-- For MySQL Database Driver: -->
> org.gjt.mm.mysql.Driver
> </param-value>
> </init-param>
>
>I get this error in my sitemap.log
>ERROR (2002-06-12) 12:02.09:800
>[sitemap.generator.serverpages](/cocoon/xsp/esql)
>HttpProcessor[8080][4]/esql_xsp: Could not get the datasource
>org.apache.avalon.excalibur.datasource.NoValidConnectionException: No
>valid JdbcConnection class available
> at
>org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:183)
> at
>org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable(ResourceLimitingPool.java:491)
> at
>org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:140)
> at
>org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:81)
> at
>org.apache.avalon.excalibur.pool.ResourceLimitingPool.get(ResourceLimitingPool.java:314)
> at
>org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:91)
> at
>org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:131)
> at
>org.apache.cocoon.www.docs.samples.xsp.esql_xsp.generate(/opt2/jakarta-tomcat-4.0.4-b3/work/Standalone/localhost/cocoon/cocoon-files/org/apache/cocoon/www/docs/samples/xsp/esql_xsp.java:338)
>
>
>Any ideas other than "use jdk 1.3.1"? Is this a JNDI problem or a JDBC
>problem?
>
>Thanks.
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: NoValidConnectionException: No valid JdbcConnection class available
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Brian P. Millett [mailto:bpm@ec-group.com]
>
> Configuration:
> Using CATALINA_BASE: /opt2/jakarta-tomcat-4.0.4-b3
> Using CATALINA_HOME: /opt2/jakarta-tomcat-4.0.4-b3
> Using CATALINA_TMPDIR: /opt2/jakarta-tomcat-4.0.4-b3/temp
> Using JAVA_HOME: /usr/j2se
>
> Solaris 8, jdk 1.4, postgresql 7.2, mysql 4.01
...
> I get this error in my sitemap.log
> ERROR (2002-06-12) 12:02.09:800
> [sitemap.generator.serverpages](/cocoon/xsp/esql)
> HttpProcessor[8080][4]/esql_xsp: Could not get the datasource
> org.apache.avalon.excalibur.datasource.NoValidConnectionException: No
> valid JdbcConnection class available
> at
>
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance
(JdbcC
> onnectionFactory.java:183)
...
>
> Any ideas other than "use jdk 1.3.1"?
That's easy. Recompile excalibur.
> Is this a JNDI problem or a JDBC
> problem?
Java 1.3/1.4 JDBC incompatibility.
Vadim
>
> Thanks.
> --
> Brian Millett
> Enterprise Consulting Group "Shifts in paradigms
> (314) 205-9030 often cause nose bleeds."
> bpm@ec-group.com Greg Glenn
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>