You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Mick Knutson <mi...@gmail.com> on 2008/01/15 00:41:15 UTC
[c1.1] derby issue with .lck files not being cleaned up
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
---
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 15, 2008 12:29 PM, Mick Knutson <mi...@gmail.com> wrote:
> I have been running derby almost file. But when I bounce Tomcat, the
> db.lckfiles are not removed, thus giving me an error when I re-start
> Tomcat as the
> DB is already in use, which it is not. It is only because the lck files are
> still present.
>
> When I delete those 2 files, then re-start tomcat, everything is fine.
So you've mentioned. And this seems to happen when using embedded
Derby. The suggestion, then, is to use a standalone database. Derby
Network Server is one of the options, since your preferred choice of
Oracle 10g doesn't work.
Here's the page I mentioned earlier. Adjust as necessary...
http://docs.codehaus.org/display/MAVENUSER/Archiva+User+DB+on+Derby+Network+Server
--
Wendy
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Mick Knutson <mi...@gmail.com>.
I have been running derby almost file. But when I bounce Tomcat, the
db.lckfiles are not removed, thus giving me an error when I re-start
Tomcat as the
DB is already in use, which it is not. It is only because the lck files are
still present.
When I delete those 2 files, then re-start tomcat, everything is fine.
On Jan 15, 2008 11:22 AM, Wendy Smoak <ws...@gmail.com> wrote:
> On Jan 15, 2008 12:13 PM, Mick Knutson <mi...@gmail.com> wrote:
> > Trust me, I do NOT want to use Derby, but there is an Oracle bug:
> > http://jira.codehaus.org/browse/CONTINUUM-1622
> >
> > Thus I am forced to use Derby for now until that is fixed. So, any help
> to
> > get this fixed on Derby until the above bug is fixed would be great....
>
> You can run Derby in standalone mode as Derby Network Server. I think
> there are some instructions on either the Archiva or Continuum wiki.
> If it's Archiva, the instructions will be very similar for Continuum.
>
> --
> 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
---
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 15, 2008 12:13 PM, Mick Knutson <mi...@gmail.com> wrote:
> Trust me, I do NOT want to use Derby, but there is an Oracle bug:
> http://jira.codehaus.org/browse/CONTINUUM-1622
>
> Thus I am forced to use Derby for now until that is fixed. So, any help to
> get this fixed on Derby until the above bug is fixed would be great....
You can run Derby in standalone mode as Derby Network Server. I think
there are some instructions on either the Archiva or Continuum wiki.
If it's Archiva, the instructions will be very similar for Continuum.
--
Wendy
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Mick Knutson <mi...@gmail.com>.
Trust me, I do NOT want to use Derby, but there is an Oracle bug:
http://jira.codehaus.org/browse/CONTINUUM-1622
Thus I am forced to use Derby for now until that is fixed. So, any help to
get this fixed on Derby until the above bug is fixed would be great....
On Jan 15, 2008 12:16 AM, Emmanuel Venisse <em...@gmail.com>
wrote:
> 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 <mi...@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
> > ---
> >
>
--
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
---
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Emmanuel Venisse <em...@gmail.com>.
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 <mi...@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
> ---
>
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Mick Knutson <mi...@gmail.com>.
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 <ws...@gmail.com> wrote:
> On Jan 14, 2008 4:41 PM, Mick Knutson <mi...@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
---
Re: [c1.1] derby issue with .lck files not being cleaned up
Posted by Wendy Smoak <ws...@gmail.com>.
On Jan 14, 2008 4:41 PM, Mick Knutson <mi...@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