2

Hi, We get the following error message in the log when deploying 488. The issue does not seem to block accessing the application or anything. It occurs exactly every 5 minutes. Does anyone know what could be causing this? Thanks. EDIT: error message seems to be caused by a scheduled event (widget > not the standard ones) microflow that was renamed in the latest deployment. Apparently this causes issues. Once I unscheduled the flow, the error messages stopped. 20141111 EDIT: As of yesterday the issue suddenly returned in our test environment. Software was not changed. IT did add a CPU to the VM configuration (but all VMs and applications involved were stopped and started afterwards). No scheduled events are running at the moment. Behaviour is identical, every 5 minutes the error is present in the log. 20141113 EDIT: As of today the error messages suddenly disappeared, no new deployment or restart was done. Although the issue did not seem to do any damage it is kind of annoying that we do not know what is causing it. Anyone any clue on its origins? 20150112 EDIT/RESOLUTION: Logged a call at Mendix support. They indicated that I could resolve the issue by ensuring that some entries in System.Session are removed. Apparently something goes wrong cleaning the sessions. We added a startup flow action deleting all entries in the Session object. Cleaning all sessions at the moment of a restart. This resolved our issue and we never encounter the error anymore. However, Mendix should resolve the root cause of the issue. 2014-09-29 14:40:32.698 ERROR - Core: Cluster manager failed to destroy session'906c1234-959d-4b2a-9410-3a0d5c7a409e', probably caused by a lock or running transaction on the database. 2014-09-29 14:40:32.698 ERROR - Core: java.lang.IllegalArgumentException: Session '906c1234-959d-4b2a-9410-3a0d5c7a409e' is not managed by the session manager at jg.a(SourceFile:251) at he.a(SourceFile:222) at he.d(SourceFile:207) at he.c(SourceFile:184) at he.b(SourceFile:146) at he.a(SourceFile:68) at he.execute(SourceFile:29) at com.mendix.core.actionmanagement.CoreAction.a(SourceFile:478) at com.mendix.core.actionmanagement.CoreAction.call(SourceFile:463) at hJ.b(SourceFile:198) at ia.c(SourceFile:36) at hY$b$a.apply(SourceFile:138) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.a(SourceFile:185) at com.mendix.externalinterface.connector.RequestDispatching$Worker$a.apply(SourceFile:179) at akka.actor.Actor$class.apply(Actor.scala:545) at com.mendix.externalinterface.connector.RequestDispatching$Worker.apply(SourceFile:175) at akka.actor.LocalActorRef.invoke(ActorRef.scala:910) at akka.dispatch.MessageInvocation.invoke(MessageHandling.scala:25) at akka.dispatch.ExecutableMailbox$class.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:223) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.processMailbox(ExecutorBasedEventDrivenDispatcher.scala:123) at akka.dispatch.ExecutableMailbox$class.run(ExecutorBasedEventDrivenDispatcher.scala:195) at akka.dispatch.ExecutorBasedEventDrivenDispatcher$$anon$4.run(ExecutorBasedEventDrivenDispatcher.scala:123) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at akka.dispatch.MonitorableThread.run(ThreadPoolBuilder.scala:192)

asked 2014-09-29

1 answers