Sorry All,

I hadn't noticed that the user already resolved his problem.  And perhaps 
it was not at all similar to mine.

For me the question still remains: why exactly did the HSQLDB default to 
using a secure socket.

Has anyone seen this behavior before?  I couldn't find anything in the 
documentation on HSQLDB.

Thanks,

-doug

[email protected] wrote on 02/20/2009 04:15:15 PM:

> 
> I worked through the same problem on Redhat Linux running Java 1.5.: 
> 
> ------- 
> Message: Failure occured during job recovery. 
> 
> Description: 
> org.apache.avalon.framework.configuration.ConfigurationException: cannot 

> create a quartz scheduler 
> 
> Sender: org.apache.cocoon.servlet.CocoonServlet 
> 
> Source: Cocoon Servlet 
> 
> cause 
> 
> org.quartz.SchedulerConfigException: Failure occured during job 
> recovery. [See nested exception: org.quartz.JobPersistenceException: 
> Failed to obtain DB connection from data source 
> 'excalibur:LenyaScheduler': java.sql.SQLException: Database does not 
> exists in statement [cocoondb] [See nested exception: 
> java.sql.SQLException: Database does not exists in statement 
[cocoondb]]] 
> 
> -------- 
> 
> In short the problem occured because HSQLDB constructed in: 
> 
> apache-lenya-2.0.2-
> 
src/externals/cocoon_2_1_x/src/blocks/hsqldb/java/org/apache/cocoon/components/hsqldb/ServerImpl.
> java 
> 
> is defaulting to using a secure socket.  I modified this file to 
> explicitly set using a secure socket to false, Lenya 2.0.2 began to 
> work as expected. 
> 
> I could supply a patch for you try if you'd like, however, this 
> means patching your local copy of cocoon. 
> 
> Perhaps one of the dev's can suggest the best place to get this 
> patched permanently.  Or whether its a known issue with cocoon 2.1.xor 
hsqldb.
> 
> Hope that helps.  And let me know if you'd be interested in a patch. 
> 
> -doug

Reply via email to