Tomcat restart definitively solves the problem (maybe for a while)
but the unsaved content is lost (logically)
could we at least have some notification (js, html) if the save fails
like in this case ??
then we can restart tomcat on time, before adding (unsuccessfully)
20-30 paragraphs, documents, etc...
Stojan
(Michael Aemisegger) wrote:
I sometimes had exactly the same problem. If I recall correctly on a
Magnolia 2.0 system. I'm not sure whether it also happened on 2.1. If
I encounter the error again I will share the information.
I also suspect that multi user access creates these kind of problems.
I think it has to do how repository session are handled. I don't know
which part of the system is responsible for that behaviour. It could
be Jackrabbit, Magnolia or my own code.
To stabilize the system, a restart of tomcat was needed in my case.
Unfortunately, some changes to the content will then get lost.
I never could clearly identify the source of the problem and
unfortunately can not provide a solution.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
