It looks like an Akka issue or more accurately your question requires a level of knowledge in Akka which I personally do not have. On 5/13/2016 11:15, Suraj Mundada wrote:

Hi,

I am using Play 2.4.6 on CentOS 6 server with Java 8 for deploying production application. I am using logback logging in Akka actors for doing my async tasks and sending email is one the tasks.

From last 2 days, I am getting following exception:

|akka.ConfigurationException:Couldnot start logger due to [akka.ConfigurationException:Logger specified in config can't be loaded [akka.event.Logging$DefaultLogger] due to [akka.event.Logging$LoggerInitializationException: Logger log1-Logging$DefaultLogger did not respond with LoggerInitialized, sent instead [TIMEOUT]]] at akka.event.LoggingBus$class.startDefaultLoggers(Logging.scala:144) at akka.event.EventStream.startDefaultLoggers(EventStream.scala:26) at akka.actor.LocalActorRefProvider.init(ActorRefProvider.scala:623) at akka.actor.ActorSystemImpl.liftedTree2$1(ActorSystem.scala:620) at akka.actor.ActorSystemImpl._start$lzycompute(ActorSystem.scala:617) at akka.actor.ActorSystemImpl._start(ActorSystem.scala:617) at akka.actor.ActorSystemImpl.start(ActorSystem.scala:634) at akka.actor.ActorSystem$.apply(ActorSystem.scala:142) at akka.actor.ActorSystem$.apply(ActorSystem.scala:109) at akka.actor.ActorSystem$.create(ActorSystem.scala:57) at akka.actor.ActorSystem.create(ActorSystem.scala) at manager.EmailManager.sendHtmlEmail(EmailManager.java:63) at|

My application.conf has below entry:

| akka { loggers = ["akka.event.slf4j.Slf4jLogger"] loglevel = "DEBUG" logging-filter = "akka.event.slf4j.Slf4jLoggingFilter" event-handlers = ["akka.event.slf4j.Slf4jEventHandler"] default-dispatcher { fork-join-executor { parallelism-min = 8 } } } |

logback.xml has following entries apart from other appender and logger declarations:

| <logger name="play" level="INFO" /> <logger name="application" level="DEBUG" /> <logger name="akka" level="INFO" />

|

However, I do not use akka logger reference defined above anywhere in my code. Instead, I use default logger configuration where timeout is happening:

| Logger.debug("EmailActor - onReceive() : MultiPartEmail message to xyz@abc.com <mailto:xyz@abc.com>");

|

Each time timeout happens, I have to restart my play application.

Is it hardware issue which is restricting threads available for creating new actor instances or causing timeout for logger? or something else?

My production box is 1 Core 4 GB with CentOS 6 and play application runs within a docker on this box.

Regards, Suraj