Cluster journal reset?

[Chris Schmidt <cs...@prospricing.com>]

Hi,

 

  We are using an internal Jackrabbit repository to store metadata
information for a product.  Currently, we use clustering to allow
multiple processes to interact with the information.  I've noticed an
issue when users wipe out their database without deleting the installed
product.  It seems information in the workspace has some information
(possibly the journal revision number?) that becomes out of sync when
the JCR tables are recreated.  I cannot add or find information through
jackrabbit afterwards.  The only way to get beyond this problem is the
manually delete the repository directory as well.  We are configured to
have everything in the database, and thought the only information on the
filesystem would be the lucene index.

 

  Is there a way to detect and reset the information on the filesystem
without having to delete it completely?

 

Thanks,

 

  Chris

 

Re: Anybody using DB2?

[Esteban Franqueiro <es...@bea.com>]

> hi esteban
>
> On Wed, Mar 26, 2008 at 6:01 PM, Esteban Franqueiro
> <es...@bea.com> wrote:
>> Hi all!
>>  I was wondering if anybody is using DB2. Since there's no bundle PM for it, maybe it's because 
>> the
>>  BundleDbPM works fine?
>
> there's a db2.ddl resource. use BundleDbPersistenceManager and specify
> "db2" for the "schema"
> parameter, i.e.
>
>   <param name="schema" value="db2"/>
>
> the vendor-specific PM classes are only there because they need to
> override some base class methods.
>
> cheers
> stefan

Thanks Stefan!

Esteban Franqueiro
esteban.franqueiro@bea.com 


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Re: Anybody using DB2?

[Stefan Guggisberg <st...@gmail.com>]

hi esteban

On Wed, Mar 26, 2008 at 6:01 PM, Esteban Franqueiro
<es...@bea.com> wrote:
> Hi all!
>  I was wondering if anybody is using DB2. Since there's no bundle PM for it, maybe it's because the
>  BundleDbPM works fine?

there's a db2.ddl resource. use BundleDbPersistenceManager and specify
"db2" for the "schema"
parameter, i.e.

   <param name="schema" value="db2"/>

the vendor-specific PM classes are only there because they need to
override some base class methods.

cheers
stefan

>  Also, there's a DB2FileSystem, but no bundle DB PM.
>  Summing up... Does Jackrabbit work storing everything in DB2?
>  Thanks!
>
>  Esteban Franqueiro
>  esteban.franqueiro@bea.com
>
>
>  Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
>

Anybody using DB2?

[Esteban Franqueiro <es...@bea.com>]

Hi all!
I was wondering if anybody is using DB2. Since there's no bundle PM for it, maybe it's because the 
BundleDbPM works fine?
Also, there's a DB2FileSystem, but no bundle DB PM.
Summing up... Does Jackrabbit work storing everything in DB2?
Thanks!

Esteban Franqueiro
esteban.franqueiro@bea.com 


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

Re: Cluster journal reset?

[Alessandro Bologna <al...@gmail.com>]

Hi,
there's a file called revision.log inside each cluster's node repository
directory (it should be just 8 bytes long). We usually delete that and
usually works (using the DB backed journal).
Alessandro



On Wed, Mar 26, 2008 at 11:42 AM, Chris Schmidt <cs...@prospricing.com>
wrote:

> Hi,
>
>
>
>  We are using an internal Jackrabbit repository to store metadata
> information for a product.  Currently, we use clustering to allow
> multiple processes to interact with the information.  I've noticed an
> issue when users wipe out their database without deleting the installed
> product.  It seems information in the workspace has some information
> (possibly the journal revision number?) that becomes out of sync when
> the JCR tables are recreated.  I cannot add or find information through
> jackrabbit afterwards.  The only way to get beyond this problem is the
> manually delete the repository directory as well.  We are configured to
> have everything in the database, and thought the only information on the
> filesystem would be the lucene index.
>
>
>
>  Is there a way to detect and reset the information on the filesystem
> without having to delete it completely?
>
>
>
> Thanks,
>
>
>
>  Chris
>
>
>
>