You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2002/01/04 00:19:30 UTC

HSQLDB Shutdown

Hi,

Right now everybody (yes, everybody!) is experiencing IO exception when 
starting the Cocoon (second time) with HSQLDB - that's because database
is 
not correctly shut down after first run. When I patched this, 
I found another problem on the way: org.hsqldb.ServerConnection executes

System.exit() after executing SHUTDOWN SQL command.

Can anybody escalate this issue with HSQLDB team?
Or, is there any other ways to solve the issue?

Regards,
Vadim



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


Re: HSQLDB Shutdown

Posted by Jeff Turner <je...@socialchange.net.au>.
On Thu, Jan 03, 2002 at 06:19:30PM -0500, Vadim Gritsenko wrote:
> Hi,
> 
> Right now everybody (yes, everybody!) is experiencing IO exception when 
> starting the Cocoon (second time) with HSQLDB - that's because database
> is 
> not correctly shut down after first run. When I patched this, 
> I found another problem on the way: org.hsqldb.ServerConnection executes
> 
> System.exit() after executing SHUTDOWN SQL command.
> 
> Can anybody escalate this issue with HSQLDB team?
> Or, is there any other ways to solve the issue?

You could set a SecurityManager that lacks the "exitVM"
RuntimePermission, and then catch the resulting SecurityException.

(idea courtesy of Bob Kerns, who suggested it on ant-dev, resulting in a
stunned silence..

http://marc.theaimsgroup.com/?l=ant-dev&m=100980000205533&w=2
)


--Jeff

> Regards,
> Vadim

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


RE: HSQLDB Shutdown

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
> 
> I tried your tip... Seems it is working Ok; no data loss found. So I
> patched ServerImpl to remove this backup file right before starting up
> HSQL server.
> 
> Hope this is Ok.
> 

It works here as well.

Thanks,
Carsten

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


RE: HSQLDB Shutdown

Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>
> Vadim Gritsenko wrote:
> >
> > > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]

<snip/>

> > > I know this is a hack, but perhaps also deleteing the backup file
> > > might solve the problem. I always delete it before restarting
Cocoon,
> > > and this avoids all io exceptions.
> >
> > Just tell me how to explain this to the end users - or Cocoon app
> > developers
> > who decided to use HSQLDB! :)
> >
> Hm, we could put it into the FAQ, but I thought of adding this to your
> patch: when the hsqldb is shutdown, the file is remvoed. Don't know if
this
> has any site-effect, but it might help.

I tried your tip... Seems it is working Ok; no data loss found. So I
patched ServerImpl to remove this backup file right before starting up
HSQL server.

Hope this is Ok.

Regards,
Vadim


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


RE: HSQLDB Shutdown

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
> 
> > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > 
> > Vadim Gritsenko wrote:
> > >
> > > Hi,
> > >
> > > Right now everybody (yes, everybody!) is experiencing IO exception
> when
> > > starting the Cocoon (second time) with HSQLDB - that's because
> database
> > > is
> > > not correctly shut down after first run. When I patched this,
> > > I found another problem on the way: org.hsqldb.ServerConnection
> executes
> > >
> > > System.exit() after executing SHUTDOWN SQL command.
> > >
> > > Can anybody escalate this issue with HSQLDB team?
> > > Or, is there any other ways to solve the issue?
> > >
> > 
> > What did your patch include? Sending the shutdown SQL command?
> 
> Yes.
> 
> > 
> > I know this is a hack, but perhaps also deleteing the backup file
> > might solve the problem. I always delete it before restarting Cocoon,
> > and this avoids all io exceptions.
> 
> Just tell me how to explain this to the end users - or Cocoon app
> developers
> who decided to use HSQLDB! :)
> 
Hm, we could put it into the FAQ, but I thought of adding this to your
patch: when the hsqldb is shutdown, the file is remvoed. Don't know if this
has any site-effect, but it might help.

Carsten

> Vadim
> 
> > 
> > Carsten
> >
> 
> 
> 
> ---------------------------------------------------------------------
> 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


RE: HSQLDB Shutdown

Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> 
> Vadim Gritsenko wrote:
> >
> > Hi,
> >
> > Right now everybody (yes, everybody!) is experiencing IO exception
when
> > starting the Cocoon (second time) with HSQLDB - that's because
database
> > is
> > not correctly shut down after first run. When I patched this,
> > I found another problem on the way: org.hsqldb.ServerConnection
executes
> >
> > System.exit() after executing SHUTDOWN SQL command.
> >
> > Can anybody escalate this issue with HSQLDB team?
> > Or, is there any other ways to solve the issue?
> >
> 
> What did your patch include? Sending the shutdown SQL command?

Yes.

> 
> I know this is a hack, but perhaps also deleteing the backup file
> might solve the problem. I always delete it before restarting Cocoon,
> and this avoids all io exceptions.

Just tell me how to explain this to the end users - or Cocoon app
developers
who decided to use HSQLDB! :)

Vadim

> 
> Carsten
>



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


RE: HSQLDB Shutdown

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
>
> Hi,
> 
> Right now everybody (yes, everybody!) is experiencing IO exception when 
> starting the Cocoon (second time) with HSQLDB - that's because database
> is 
> not correctly shut down after first run. When I patched this, 
> I found another problem on the way: org.hsqldb.ServerConnection executes
> 
> System.exit() after executing SHUTDOWN SQL command.
> 
> Can anybody escalate this issue with HSQLDB team?
> Or, is there any other ways to solve the issue?
> 

What did your patch include? Sending the shutdown SQL command?

I know this is a hack, but perhaps also deleteing the backup file
might solve the problem. I always delete it before restarting Cocoon,
and this avoids all io exceptions.

Carsten

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