cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Watson" <cwat...@taraserv.demon.co.uk>
Subject RE: SOLVED: Pool: NoValidConnectionException on jdk1.4 -> Berin, please read this
Date Fri, 29 Mar 2002 15:43:37 GMT
> -----Original Message-----
> From: Enke Michael [mailto:Michael.Enke@wincor-nixdorf.com]
> Sent: 29 March 2002 08:21
> To: cocoon-dev@xml.apache.org
> Subject: SOLVED: Pool: NoValidConnectionException on jdk1.4 -> Berin,
> please read this
>
>
> Hi,
> Tonight I found the solution:
> We have a ClassCastException. To solve this for jdk1.4:
> Get the daily build from excalibur,
> change both JdbcConnection to Jdbc3Connection in line 106 in
> scratchpad/org/apache/avalon/excalibur/datasource/ResourceLimi
> tingJdbcConnectionPool.java
> Thats it. But - THIS IS ONLY FOR JDK1.4, this doesn't wor for
> jdk < 1.4

I tried this. I had a bit of fun getting the daily build to build - I'm
assuming you do this from build in the all directory?
I had to drop log4j out of logger, move cli and instrument to under all, use
the latest development jars for logkit and framework etc, blah blah
Eventually got it to compile, put all the jars into cocoon, rebuilt that ...

Start tomcat, which complains about not being able to start cocoon logger

Now it works EVERY ALTERNATE TIME ?? I run the xsp/esql example

First time it works.
Hit refresh and it fails with

Original exception : java.lang.RuntimeException: Could not get the
datasource
org.apache.avalon.excalibur.datasource.NoAvailableConnectionException:
org.apache.avalon.excalibur.datasource.Jdbc3Connection
at
org.apache.cocoon.www.docs.samples.xsp.agsql_xsp.generate(X:\jakarta-tomcat-
4.0.4b1\work\localhost\cocoon\cocoon-files\org/apache/cocoon/www/docs/sample
s/xsp\agsql_xsp.java:341)
at
org.apache.cocoon.generation.ServerPagesGenerator.generate(ServerPagesGenera
tor.java:260)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEv
entPipeline.java:251)
at
org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingS
treamPipeline.java:399)
at
org.apache.cocoon.www.sitemap_xmap.matchN4007D4(X:\jakarta-tomcat-4.0.4b1\wo
rk\localhost\cocoon\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:985
7)
at
org.apache.cocoon.www.sitemap_xmap.process(X:\jakarta-tomcat-4.0.4b1\work\lo
calhost\cocoon\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:3675)
at
org.apache.cocoon.www.sitemap_xmap.process(X:\jakarta-tomcat-4.0.4b1\work\lo
calhost\cocoon\cocoon-files\org/apache/cocoon/www\sitemap_xmap.java:3085)
at org.apache.cocoon.sitemap.Handler.process(Handler.java:222)
at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:179)
at org.apache.cocoon.sitemap.SitemapManager.process(SitemapManager.java:154)
at org.apache.cocoon.Cocoon.process(Cocoon.java:575)
at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:998)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

and I can see the port connections getting dropped

Hit refresh and it works again.
Hit refresh and it fails again as above.

Eventually, I get nothing back at all

:-{

Is this just me?
If not, is it something that could be fixed soon, or would you advise me to
go back to jdk1.3 for the while ??

> To make it relly nice to work for all, Berin will sourround it with
> if(instance of JdbcConnection) ... else if(instance of
> Jdbc3Connection) or something like this,
> won't you Berin?
>
> Happy easter again,
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message