[MAGNOLIA-1848] Updating from 3.0.5: RepositoryException while logging in Created: 15/Nov/07  Updated: 23/Jan/13  Resolved: 16/Nov/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5 RC1
Fix Version/s: 3.5 RC2

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

Attachments: Text File Update-3.0.5-to-3.5-RepositoryException-on-login.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   

Note: this definitely not a blocking issue and does not affect security at all.

The exception is:
DEBUG info.magnolia.cms.security.MgnlUser MgnlUser.java(setLastAccess:407) 15.11.2007 22:45:12 Unable to set the last access date due to a javax.jcr.RepositoryException - /system/superuser/lastaccess: cannot save a new item.
javax.jcr.RepositoryException: /system/superuser/lastaccess: cannot save a new item.

See the full error stack trace in the file attached.

To reproduce the error:

  • bootstrap clean 3.0.5; stop tomcat
  • remove all jar files in WEB-INF lib and put in those of 3.5RC1
  • start tomcat; perform installation
  • logging in as superuser (and on subsequent logins; after tomcat restart as well) raises RepositoryException


 Comments   
Comment by Philipp Bracher [ 16/Nov/07 ]

Tested it on a fresh installed system. The issue occurs there as well. To see it you have to set logger to debug level.

The message should actually be logged as a warning

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