continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse" <emmanuel.veni...@gmail.com>
Subject Re: [c1.1] derby issue with .lck files not being cleaned up
Date Tue, 15 Jan 2008 08:16:11 GMT
Do you use an embedded Derby db? It would be better to use a standalone db.

Emmanuel

On Jan 15, 2008 12:41 AM, Mick Knutson <mickknutson@gmail.com> wrote:

> I am running tomcat 5.5.25 with continuum-1.1.war and a Derby DB.
>
> Now I am also running archiva 1.0 pointing to my Oracle DB. I am not using
> Oracle for both as there seems to still be a defect with continuum on
> Oracle
> 10g. But, 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.
>
> NOTE: When this issue occurs, Archiva still functions as it points to
> Oracle, and does not seem to have a tomcat issue.
>
> --
> 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