Carsten Ziegeler a écrit :
>
> Hi C2ers!
>
> I think we are all +1 on the beta question. The only real
> remaining problem is that someone has to actually do it.
>
> So here is the roadmap for beta 1 that I will follow unless
> someone kills me - or threatens to :-):
>
> - Code-freeze and testing of the examples to be completed
> by Sunday (MEST).
> Only bug fixing should be checked in from now.
> Can someone test the database examples?
They're functionnal, but there are some "message output is null" in the
tomcat's console, and the log file contains the following exception on
the Simple SQL sample.
DEBUG 84521 [cocoon ] (Thread-10): Retrieving a
org.apache.avalon.excalibur.datasource.JdbcConnection from the pool
DEBUG 84521 [cocoon ] (Thread-10): JdbcConnection was closed,
creating one to take its place
DEBUG 84521 [cocoon ] (Thread-10): JdbcConnection object created
DEBUG 84521 [cocoon ] (Thread-10): Returning a
org.apache.avalon.excalibur.datasource.JdbcConnection to the pool
WARN 84521 [cocoon ] (Thread-10): Pool interrupted while waiting
for lock.
java.lang.IndexOutOfBoundsException: Index: -1, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:491)
at java.util.ArrayList.remove(ArrayList.java:375)
at
org.apache.avalon.excalibur.pool.DefaultPool.put(DefaultPool.java:174)
at
org.apache.avalon.excalibur.datasource.JdbcConnection.close(JdbcConnection.java:134)
at
org.apache.cocoon.transformation.SQLTransformer$Query.close(SQLTransformer.java:614)
at
org.apache.cocoon.transformation.SQLTransformer$Query.next(SQLTransformer.java:597)
at
org.apache.cocoon.transformation.SQLTransformer.executeQuery(SQLTransformer.java:194)
at
org.apache.cocoon.transformation.SQLTransformer.executeQuery(SQLTransformer.java:198)
at
org.apache.cocoon.transformation.SQLTransformer.endExecuteQueryElement(SQLTransformer.java:294)
at
org.apache.cocoon.transformation.SQLTransformer.endElement(SQLTransformer.java:396)
at
org.apache.cocoon.components.sax.XMLTeePipe.endElement(XMLTeePipe.java:84)
at org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator.java:1436)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1260)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1035)
at
org.apache.cocoon.components.parser.JaxpParser.parse(JaxpParser.java:72)
at
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:115)
at
org.apache.cocoon.components.pipeline.CachingEventPipeline.process(CachingEventPipeline.java:220)
at
org.apache.cocoon.components.pipeline.CachingStreamPipeline.process(CachingStreamPipeline.java:344)
at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:3705)
at org.apache.cocoon.www.sitemap_xmap.process(sitemap_xmap.java:1337)
at org.apache.cocoon.sitemap.Handler.process(Handler.java:175)
at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:94)
at org.apache.cocoon.Cocoon.process(Cocoon.java:293)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:471)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
at org.apache.tomcat.core.Handler.service(Handler.java:286)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)
Couldn't this be caused by the connection being closed twice ? A quick
look to SQLTransformer did not reveal it, but maybe it could be worth
investigating this way.
> - Total code-freeze starting monday to prepare the distribution.
> - Release of the beta on Wednesday
>
> I will prepare the distribution and put it on Daedalus on
> Wednesday and Giacomo will write the announcement.
>
Great, great :)
> Carsten
>
--
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
