Re: [akka-user] LEAK: You are creating too many HashedWheelTimer instances

Patrik, I suspected it might be from Cassandra client driver too. I haven't seen those errors for two days. Will add the "ch.qos.logback' like you suggested below. Thank you very much! Yan On Tuesday, July 5, 2016 at 5:11:19 AM UTC-5, Patrik Nordwall wrote: > > Could it be that these are

Re: [akka-user] LEAK: You are creating too many HashedWheelTimer instances

Could it be that these are created by Netty via Cassandra client driver via akka-persistence-cassandra? You can try to add "ch.qos.logback" % "logback-classic" % "1.1.3" dependency and enable logging in logback.xml for That might show you what the Cassandra driver is doing, e.g. scheduling

Re: [akka-user] LEAK: You are creating too many HashedWheelTimer instances

We run this application via a scheduler, every three hours. We did shutdown ActorSystem at the end of each run and restart ActorSystem at the beginning of each run. Will it cause problem? Thanks, Yan On Friday, July 1, 2016 at 12:47:45 PM UTC-5, √ wrote: > > I would suspect that you may be

Re: [akka-user] LEAK: You are creating too many HashedWheelTimer instances

I would suspect that you may be creating new ActorSystem instances instead of reusing a single one. -- Cheers, √ On Jul 1, 2016 7:05 PM, "Yan Pei" wrote: > Hello All, > > I am using AKKA 2.4.4 and Cassandra 2.x. > Today I found there is an error from the thread of >

[akka-user] LEAK: You are creating too many HashedWheelTimer instances

Hello All, I am using AKKA 2.4.4 and Cassandra 2.x. Today I found there is an error from the thread of 'actor-system-cassndra-plugin-default-dispatcher-380': LEAK: You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the