Hi Michael, Sameer,
We are running QA with the new code, I will let you know if the
exception disappeared.
Up to now, we did not see any data loss, just that exception showing
up and again endlessly.
Thanks for your feedback.
Niko,
On Jun 15, 2006, at 9:27 PM, Michael Aemisegger wrote:
Hi Nico
Nicolas Modrzyk wrote:
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.
I also suffer from this problem.
The version of jackrabbit used for M2.1 is not thread safe.
Concurrent modifications can lead to following Exceptions:
javax.jcr.InvalidItemStateException
javax.jcr.RepositoryException: Unable to start edit operation:
Already in edit mode: Already in edit mode
and maybe even more.
I tried to reduce the concurrency problems by synchonizing write
access in magnolia code. Still, the problem sometimes occurs.
There's not much you can do than upgrade to a more recent version
of jackrabbit. This can mean to migrate your repository and patch
magnolia code.
Maybe you could refresh the nodes in question and try to save
again. This would only lead to partial data loss. In any case, the
user should get informed which is not the case yet in magnolia.
For the time being, you have to restart tomcat. Be aware, that all
data in your sessions that could not been saved is lost. Maybe you
have a chance to export your data from the session in question
somehow. Don't ask me how.
Hope it helps.
--
Cheers,
Michael
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
