[MAGNOLIA-358] missing shutdown for repositories might corrupt them Created: 29/Apr/05  Updated: 15/Jun/05  Resolved: 15/Jun/05

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.1 Final
Fix Version/s: 2.1 Final

Type: Bug Priority: Blocker
Reporter: Boris Kraft Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

seen with CQFS


Attachments: Text File cqfs_inode_log.txt    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Currently, repositories are not shutdown properly when magnolia is stopped.

I have seen several instances of repository corruption where at startup of magnolia, catalina.out states:

— 8< —
ERROR com.day.jackrabbit.fs.cq.CQFileSystem ?(?:?) 28.04.2005 17:41:50 failed to initialize file system
java.io.IOException: not an inode: 1
— 8< —

Unfortunately, to do a clean backup I need to shutdown magnolia, so this is a catch-22 situation.

We need to provide a hook to properly shut down repositories.

I set this to "Blocker" for hopefully obvious reasons.



 Comments   
Comment by Boris Kraft [ 29/Apr/05 ]

complete log of corrupted CQFS startup (for historic reasons)

Comment by Fabrizio Giustina [ 29/Apr/05 ]

According to jackrabbit, no explicit shutdown should be performed if the rebository is bound to a jndi context, since tomcat should take care of it.. don't know if adding a context listener can solve the problem.

Comment by Boris Kraft [ 15/Jun/05 ]

Some issues remain with CQFS on OSX 10.3.4, but otherwise afaik this has been fixed in Jackrabbit

Generated at Mon Feb 12 03:16:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.