[MAGNOLIA-586] jackrabbit session update problems Created: 27/Oct/05 Updated: 23/Jan/13 Resolved: 17/May/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1.3, 2.1.4, 3.0 Beta 1 |
| Fix Version/s: | 3.0 RC1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Boris Kraft |
| Resolution: | Fixed | Votes: | 1 |
| 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 |
|
the jcr session is not always updated if the changes are made inside an other session. It looks like this behavior appears after one has done a lot of changes. One can force this behavior doing the following:
Attention: this has nothing to do with activation you can get this also through common deletion (paralell sessions) But Karsten Wintermann reported a similar problem: .. "Sorry, I'm not able to determine the exact steps to reproduce this behavior. It happens after I edit some attributes in the "Config" repository. After some time the system enters a state where all copy and move operations reproducibly fail." .. ..." In my case I believe it had nothing to do with subscribers. Copy and Move worked fine up to a certain point, then after that they failed. I did not touch the subscriber configuration for this. I know the issue with unreachable subscribers, but this one is different." ... |
| Comments |
| Comment by Michael Aemisegger [ 27/Oct/05 ] |
|
maybe this is related to http://jira.magnolia.info/browse/MAGNOLIA-547 ? |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
we needed to synchronize changes in the same hierarchy |