Strange error after locally deploying the model a couple of times

1
After redeploying the model local a couple of times we sometimes get the error below. The machine has to be restarted again to be able to deploy again. Anybody a guess what might be causing this? Regards, Ronald access denied ("java.util.PropertyPermission" "net.sf.ehcache.store.config.alwaysPutOnHeap" "read") -------- akka.actor.ActorInitializationException: exception during creation at akka.actor.ActorInitializationException$.apply(Actor.scala:164) at akka.actor.ActorCell.create(ActorCell.scala:596) at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456) at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478) at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:263) at akka.dispatch.Mailbox.run(Mailbox.scala:219) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) Caused by: java.security.AccessControlException: access denied ("java.util.PropertyPermission" "net.sf.ehcache.store.config.alwaysPutOnHeap" "read") at java.security.AccessControlContext.checkPermission(AccessControlContext.java:372) at java.security.AccessController.checkPermission(AccessController.java:559) at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1298) at java.lang.System.getProperty(System.java:744) at net.sf.ehcache.store.MemoryStore.getAdvancedBooleanConfigProperty(MemoryStore.java:1057) at net.sf.ehcache.store.MemoryStore.<init>(MemoryStore.java:133) at net.sf.ehcache.store.NotifyingMemoryStore.<init>(NotifyingMemoryStore.java:37) at net.sf.ehcache.store.NotifyingMemoryStore.create(NotifyingMemoryStore.java:49) at net.sf.ehcache.store.MemoryOnlyStore.create(MemoryOnlyStore.java:78) at net.sf.ehcache.Cache.initialise(Cache.java:1099) at net.sf.ehcache.CacheManager.initializeEhcache(CacheManager.java:1306) at net.sf.ehcache.CacheManager.addCacheNoCheck(CacheManager.java:1337) at net.sf.ehcache.CacheManager.addCache(CacheManager.java:1235) at net.sf.ehcache.CacheManager.addCache(CacheManager.java:1177) at com.mendix.core.cache.internal.Cacher.<init>(MxObjectCacheImpl.scala:196) at com.mendix.core.cache.internal.CacheSystem$$anonfun$5.apply(MxObjectCacheImpl.scala:179) at com.mendix.core.cache.internal.CacheSystem$$anonfun$5.apply(MxObjectCacheImpl.scala:179) at akka.actor.TypedCreatorFunctionConsumer.produce(Props.scala:343) at akka.actor.Props.newActor(Props.scala:252) at akka.actor.ActorCell.newActor(ActorCell.scala:552) at akka.actor.ActorCell.create(ActorCell.scala:578) at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456) at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478) at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:263) at akka.dispatch.Mailbox.run(Mailbox.scala:219) at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
asked
1 answers
2

We did an upgrade of Ehcache in 5.10.0 to improve performance. This version apparently might run into different code paths than before, which need additional security access. You could either add this permission manually in 5.10.0 to the security file (in %INSTALL_DIR%\Mendix\5.10.0\modeler\runtemplates\deployment\data\security.policy) when running locally or ask for this permission to be added in the cloud when you are running your project there. In 5.11.0 we are not using Ehcache at all anymore to further improve performance. So upgrading to 5.11.0 would also solve your issue (both locally and in the cloud).

answered