jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg" <stefan.guggisb...@gmail.com>
Subject Re: problems with Oracle
Date Wed, 25 Oct 2006 09:20:39 GMT
On 10/24/06, Guy Spillman <gspillman@hal-inc.com> wrote:
> After JackRabbit has been properly shutdown, the
> "/locks" file record contains no data in the
> FSENTRY_DATA field.  Why keep this file after shutdown
> when no data is being stored in it?

why not? jackrabbit manages this file so there's no need
to manually remove it.

please note that this file records persistent locks, so it's
not guaranteed to be empty. if you're application creates
open-scoped (i.e. non-session-scoped) locks they will
be stored in that file.

> Also, it looks as if the Oracle JDBC driver does have
> known problems with empty LOB's (which appears to be
> the state of the FSENTRY_DATA field after shutdown).
> Take a look at this page for more information:
> http://download-east.oracle.com/docs/cd/B10501_01/appdev.920/a96591/adl03prg.htm#284807

thanks for the pointer.

now i remember, i had to add oracle specific lob-handling code to the
OraclePersistenceManager to work around this oracle 'feature'.
this code obviously didn't make it into the OracleFileSystem :(
i'll create a jira issue.


> Guy M. Spillman, Jr.
> On Tue, 24 Oct 2006 15:44:35 +0200, "Stefan Guggisberg"
> wrote:
> > the locks file is meant to be there. it contains
> > information about existing JCR locks within
> > this workspace. better not delete it!
> >
> > the repository lock file that prevents multiple
> > instantiation is a diferent story. it is cretaed in
> > the physical repository home directory.
> >
> > cheers
> > stefan
> >

View raw message