Hi Niko,
what does this last access used for? I am not sure when and how its
there because this implementation saves user node each time this
method is accessed
and for sure its vulnerable to these kind of problems since we cannot
make sure its not accessed by some background process.
if its not used anywhere I would propose to remove this from
MgnlUserManager, in future we will have audit logs which could be
used for this
Regards,
- Sameer
On Jun 15, 2006, at 1:09 PM, Nicolas Modrzyk wrote:
Hi All,
When two users log in with the same account (for example: superuser/
superuser) the logs are bombed with the same recurring exception:
javax.jcr.InvalidItemStateException ...lastAccess: the item cannot
be saved because it has been modified externally.
This is from MgnlUser.setLastAccess(l 281) ...
How we can we revert to a stable state ? The system does not
recover from it ... (as in, even after a few hours, and session
should have expired, the exception still comes back thousand of
times in the logs).
The short solution is... turn the logs off :P
Anybody has an idea what the real solution is ?
Niko,
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
