ERROR - Caching: Received a Store request for session after remove request of the session

0
Iemand ooit deze melding gezien, direct nadat een gebruikers was uitgelogd? Moet ik hier als modelleur iets mee? Feb 24 13:45:34.786 127.0.0.1 tr10000: INFO - Core: Removing session for user 'KevinLB' Feb 24 13:45:34.795 127.0.0.1 tr10000: ERROR - Caching: Received a Store request for session '58a455bc-8631-424a-a180-0aedbfe6a876' after remove request of the session. Please check no object changes are performed after logging out the session. Feb 24 13:45:34.799 127.0.0.1 tr10000: ERROR - Caching: (1/21) akka.actor.InvalidActorNameException: actor name [cacher_58a455bc-8631-424a-a180-0aedbfe6a876] is not unique! Feb 24 13:45:34.799 127.0.0.1 tr10000: ERROR - Caching: (2/21) at akka.actor.dungeon.ChildrenContainer$NormalChildrenContainer.reserve(ChildrenContainer.scala:130) Feb 24 13:45:34.799 127.0.0.1 tr10000: ERROR - Caching: (3/21) at akka.actor.dungeon.Children$class.reserveChild(Children.scala:77) Feb 24 13:45:34.799 127.0.0.1 tr10000: ERROR - Caching: (4/21) at akka.actor.ActorCell.reserveChild(ActorCell.scala:369) Feb 24 13:45:34.799 127.0.0.1 tr10000: ERROR - Caching: (5/21) at akka.actor.dungeon.Children$class.makeChild(Children.scala:202) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (6/21) at akka.actor.dungeon.Children$class.actorOf(Children.scala:38) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (7/21) at akka.actor.ActorCell.actorOf(ActorCell.scala:369) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (8/21) at com.mendix.core.cache.internal.CacheSystem.cacherForSession$1(MxObjectCacheImpl.scala:156) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (9/21) at com.mendix.core.cache.internal.CacheSystem.com$mendix$core$cache$internal$CacheSystem$$storeObject(MxObjectCacheImpl.scala:163) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (10/21) at com.mendix.core.cache.internal.CacheSystem$$anonfun$receive$1.applyOrElse(MxObjectCacheImpl.scala:129) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (11/21) at akka.actor.Actor$class.aroundReceive(Actor.scala:465) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (12/21) at com.mendix.core.cache.internal.CacheSystem.aroundReceive(MxObjectCacheImpl.scala:125) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (13/21) at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (14/21) at akka.actor.ActorCell.invoke(ActorCell.scala:487) Feb 24 13:45:34.800 127.0.0.1 tr10000: ERROR - Caching: (15/21) at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (16/21) at akka.dispatch.Mailbox.run(Mailbox.scala:220) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (17/21) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (18/21) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (19/21) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (20/21) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) Feb 24 13:45:34.801 127.0.0.1 tr10000: ERROR - Caching: (21/21) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
asked
1 answers
1

You aren't supposed to get this error, if this is something you are seeing consistently you should definitely look in to this further.

To give you some context, this is likely an action that is triggered in parallel with the logout request. It could also be something as simple as a microflow timer or datagrid refresh action which triggers at the exact same time the user logs in.
So the session is still valid when the browser sends the action to start the microflow or retrieve the data, but before the server receive the request the logout has been processed and the session has been removed.

If this is an one time incident you could ignore it, but if you see this more often I would recommend to look into this because error are never a good thing.

answered