continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mick Knutson" <mickknut...@gmail.com>
Subject Re: [c1.1] derby issue with .lck files not being cleaned up
Date Tue, 15 Jan 2008 00:13:50 GMT
Yes embedded Derby. So How do I determine why the shutdown.sh is not
shutting down Derby correctly? I used the default installation as per the
quick start guide for Tomcat and Derby. Is there something else I need to
do?


ps, http://jira.codehaus.org/browse/CONTINUUM-1622




On Jan 14, 2008 3:56 PM, Wendy Smoak <wsmoak@gmail.com> wrote:

> On Jan 14, 2008 4:41 PM, Mick Knutson <mickknutson@gmail.com> wrote:
>
> > I am running tomcat 5.5.25 with continuum-1.1.war and a Derby DB.
> ...
> > Every time run shutdown.sh to stop tomcat, then try to restart
> > running startup.sh, the following files where not cleaned up:
> >
> > /home/dapadmin/apache-tomcat-5.5.25/data/continuum/database/db.lck
> > /home/dapadmin/apache-tomcat-5.5.25/data/continuum/database/dbex.lck
> >
> > So I get an error that there is already a lock on the current database.
> > I can manually delete the locks, and restart and everything works fine.
>
> This is embedded Derby, correct?  It sounds like the database isn't
> getting shut down properly.
>
> Is there a JIRA issue open for the problem you're having with
> Continuum and Oracle 10g?
>
> --
> Wendy
>



-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message