[MAGNOLIA-577] 2.1.1 release does not always release the lock files Created: 17/Oct/05  Updated: 23/Jan/13  Resolved: 18/Oct/05

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 2.1.2
Fix Version/s: 2.1.2, 3.0 Beta 1

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

From the user list:

I installed magnolia2.1.1 for testing.

When I restart tomcat all my changes are lost. For example users or website. And only in the public instance.

from catalina.out (shutdown):
INFO info.magnolia.cms.beans.config.ShutdownManager ShutdownManager.java(contextDestroyed:52) 15.10.2005 16:34:29 Executing shutdown tasks
INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(execute:128) 15.10.2005 16:34:29 Shutting down repositories
ERROR org.apache.jackrabbit.core.RepositoryImpl RepositoryImpl.java(releaseRepositoryLock:283) 15.10.2005 16:34:29 Unable to release repository lock
ERROR org.apache.jackrabbit.core.RepositoryImpl RepositoryImpl.java(releaseRepositoryLock:283) 15.10.2005 16:34:29 Unable to release repository lock
ERROR org.apache.jackrabbit.core.RepositoryImpl RepositoryImpl.java(releaseRepositoryLock:283) 15.10.2005 16:34:29 Unable to release repository lock
ERROR org.apache.jackrabbit.core.RepositoryImpl RepositoryImpl.java(releaseRepositoryLock:283) 15.10.2005 16:34:29 Unable to release repository lock
INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(execute:128) 15.10.2005 16:34:29 Shutting down repositories
INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(execute:128) 15.10.2005 16:34:29 Shutting down repositories
INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(execute:128) 15.10.2005 16:34:29 Shutting down repositories

On startup catalina says that the repositories were not shutdown properly.

-> tomcat/webapps/magnoliaPublic/repositories/website/.lock deteteced.
-> tomcat/webapps/magnoliaPublic/repositories/config/.lock deteteced.
-> tomcat/webapps/magnoliaPublic/repositories/users/.lock deteteced.
-> tomcat/webapps/magnoliaPublic/repositories/userroles/.lock deteteced.



 Comments   
Comment by Alexandru Popescu [ 17/Oct/05 ]

The included jackrabbit version is not the good one. I have run 2.1.1 with home build jackrabbit using the following SVN versions: 321518 and 320723 and the above behavior is corrected.

./alex

.w( the_mindstorm )p.

Comment by Philipp Bracher [ 17/Oct/05 ]

The bug occures on windows systems. But the system is running properly and stable

Comment by Alexandru Popescu [ 17/Oct/05 ]

Though the initial report of this issue was from a Linux system.

./alex

.w( the_mindstorm )p.

Comment by Fabrizio Giustina [ 17/Oct/05 ]

unfortunately this is a separate bug, which was not closed by the first patch for http://issues.apache.org/jira/browse/JCR-233 (the version bundled with magnolia was deployed just after this commit)

this has been fixed in jackrabbit rev. 314930:
http://svn.apache.org/viewcvs?rev=314930&view=rev
http://issues.apache.org/jira/browse/JCR-254

Comment by Yann Lapeyre [ 09/Feb/06 ]

Tagged as fix in 2.1.2, but same problem (changes lost on each tomcat startup + unable to realease lock) on Linux with magnolia 2.1.3.

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