Home/ Questions/Q 7997849
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T15:03:58+00:00

I can’t get Akka schedule method to work properly in Heroku. It works fine

  • 0

I can’t get Akka schedule method to work properly in Heroku. It works fine locally and prints out “Heartbeat” to the log.

Here is the file in question: https://github.com/magnusart/actor-test/blob/master/app/Global.scala and snippet below.

override def onStart(app: Application) {
    Logger.debug("Starting application")
    Akka.system(app).scheduler.schedule(2 seconds, 10 seconds) {
      Logger.debug("Heartbeat")
    }
  }

The full application is here (isolated for this purpose, also on actor-test.herokuapp.com).
https://github.com/magnusart/actor-test

What does happen after startup is that I see Starting application in the logs and then I don’t see anything further after that:

2012-05-26T16:29:40+00:00 heroku[web.1]: Starting process with command `target/start -Dhttp.port=43943 -Xmx384m -Xss512k -XX:+UseCompressedOops`
2012-05-26T16:29:41+00:00 app[web.1]: Play server process ID is 3
2012-05-26T16:29:42+00:00 app[web.1]: [debug] application - Starting application
2012-05-26T16:29:42+00:00 app[web.1]: [info] play - Starting application default Akka system.
2012-05-26T16:29:42+00:00 app[web.1]: [info] play - Application started (Prod)
2012-05-26T16:29:42+00:00 app[web.1]: [info] play - Listening for HTTP on port 43943...

So the scheduled actor doesn’t actually seem to start (which it of course does locally). I’m on Heroku Cedar. I grateful for any hints as to why this isn’t working, what am I missing?

BR Magnus Andersson

Update
From what I’ve found, this seems to be a bug in Play 2 (I’m running version 2.0.1) and not be related to Heroku. I have updated a Play 2 Lighthouse ticket with relevant information. The ticket can be found here: https://play.lighthouseapp.com/projects/82401-play-20/tickets/448-play-dist-ignores-loggerxml#ticket-448-5

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem seems to come from your logger setting, because in your Heartbeat you print a message with the “debug” level.
    AFAIK, Heroku runs your Play app in “production” mode (= “play start”), ie the log level is set to “info” so the debug messages are never printed on Heroku.

    • 0