[MAGNOLIA-2029] If anonymous user is not found magnolia can corrupt the user repository Created: 26/Jan/08 Updated: 23/Jan/13 Resolved: 31/Jan/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.5.3 |
| Fix Version/s: | 3.5.4 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| 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 |
|
Ok, this is pretty difficult to explain since the principal cause is still unknown but I saw it several times... Happened only on a clustered instance with a jackrabbit bundle db persistence manager on ms sql server (since magnolia 3.1 milestones to 3.5.3):
the only way to restore it is to shut down all the instances, restart only one of the, log into magnolia as a superuser and delete manually all the additional "anonymous" users. I am debugging this problem, but I don't still have any clue on why the anonymous user couldn't be found. Looks like a jackrabbit bug but it's really strange. |
| Comments |
| Comment by Fabrizio Giustina [ 27/Jan/08 ] |
|
committed a patch that at least alleviates the original problem.
Please review the patch to check if you can see any potential issue with that! |
| Comment by Magnolia International [ 28/Jan/08 ] |
|
please don't "close", esp. if you're asking for a review |