Hi,
I'm getting some odd behaviour when activating content on 3.6.1 - it snormally eems to be working, except I'm getting some log messages that make me nervous: Everytime a node is activated I get a message saying "session has already been closed <repository name here>". Also when activating lots of stuff at once the UI in the authoring instance is giving up and returning before the activation has finished - I guess some kind of timeout - usually the page then refreshes wrongly (for instance not listing subnodes under the node you just activated). In the background the server still carries on with the activation because I can see stuff continuing to scroll through the log files.

Since the activation seemed to work yesterday, I ignored these things- but when I came in this morning my public instance seemed to be utterly broken. Looking at published pages resulted in the server returning "resource not found" pages. Restarting the server and trying to look at a page resulted in a message being logged saying that it didn't have a mime type for "jspx", which was weird. Permissions for the admin area were messed up so I couldn't actually get in to change anything (trying to look at admin central wouldn't ask me to log in - i'd see an empty admin central saying I was logged in as anonymous). In short, the whole thing seemed utterly hosed so I tore it all down and re-installed. The thing is that it was all working when I left it last night. The only explanation I can think of is that maybe there was a weird caching problem ? Or maybe permissions for "anonymous" got corrupted somehow ?

While I've been writing this I've been trying to do another activation of a large number of pages. It seems to have failed after getting most of the way through with an exception :"error writing request body to server". The problem seems to be a java IO exception.

Josh

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to