cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Savory" <s...@andrewsavory.com>
Subject Re: Avoiding a persistent startup error
Date Fri, 15 Feb 2008 09:55:54 GMT
Hi,

On 14/02/2008, Bertrand Delacretaz <bdelacretaz@apache.org> wrote:
>
> > Message: The repository home at
> > /usr/local/jakarta-tomcat-4.1.31
> /webapps/cocoon/samples/blocks/jcr/repotest
> > appears to be in use. If you are sure it's not in use please delete the
> file
> > at
> > /usr/local/jakarta-tomcat-4.1.31
> /webapps/cocoon/samples/blocks/jcr/repotest/.lock.
>
> > Probably the repository was not shutdown properly. ...
>
> This comes from the jcr block, if you're not using that block you
> should exclude it from your build.
>
> Or (again if you're not using the JCR block, as that would be where
> its data is stored), modify your startup scripts to remove that lock
> file before starting Cocoon.


I notice you have the samples in your deployment too
(webapps/cocoon/samples) - it's best practice to exclude the samples from
your build when deploying to production.



Andrew.
--
Sourcesense: Making sense of Open Source
Tel: +44 (0)870 741 6658  Fax: +44 (0)700 598 1135
Web: http://www.sourcesense.com/

Mime
View raw message