Play Scheduled async tasks don't fire on Heroku
My Play v2.6 app uses scheduled tasks. These work when run locally, but never fire when deployed to Heroku.
There are previous questions related to this, but none have a relevant answer.
The logging when setting the task is printed, but the log messages when the task is executed does not appear. Also, the effect of the task being executed never happens.
The schedule is for 1 second in the future, so there's no chance for Heroku to be sleeping the app.
The source:
@Singleton
class PaymentProcessor @Inject()(repo: PaymentRepo,
config: Configuration,
system: ActorSystem) {
private val actor = system.actorOf(Props(new ActorDef()))
private implicit val ec: ExecutionContextExecutor = system.dispatcher
def checkForPayments(reason: String, after: FiniteDuration = 1.second): Unit = {
Logger.debug(s"Checking again for due payments after $after")
system.scheduler.scheduleOnce(after, actor, CheckForPayments(reason))
}
class ActorDef() extends Actor {
override def receive: Receive = {
case CheckForPayments(reason) =>
Logger.debug(s"Checking for due payments ($reason)")
// followed by logic to find and transact due payments
}
}
Here's the unabbreviated source.
The output locally:
[debug] application - Checking again for due payments after 1 second
[debug] application - Checking for due payments (CSV uploaded)
(after which, due payments are found & transacted)
The output on Heroku:
2018-11-18T11:48:01.247773+00:00 app[web.1]: [debug] application - Checking again for due payments after 1 second
(after which due payments are not transacted)
Is this just a limitation of the free tier of Heroku? Or is there something I can configure?
heroku playframework
add a comment |
My Play v2.6 app uses scheduled tasks. These work when run locally, but never fire when deployed to Heroku.
There are previous questions related to this, but none have a relevant answer.
The logging when setting the task is printed, but the log messages when the task is executed does not appear. Also, the effect of the task being executed never happens.
The schedule is for 1 second in the future, so there's no chance for Heroku to be sleeping the app.
The source:
@Singleton
class PaymentProcessor @Inject()(repo: PaymentRepo,
config: Configuration,
system: ActorSystem) {
private val actor = system.actorOf(Props(new ActorDef()))
private implicit val ec: ExecutionContextExecutor = system.dispatcher
def checkForPayments(reason: String, after: FiniteDuration = 1.second): Unit = {
Logger.debug(s"Checking again for due payments after $after")
system.scheduler.scheduleOnce(after, actor, CheckForPayments(reason))
}
class ActorDef() extends Actor {
override def receive: Receive = {
case CheckForPayments(reason) =>
Logger.debug(s"Checking for due payments ($reason)")
// followed by logic to find and transact due payments
}
}
Here's the unabbreviated source.
The output locally:
[debug] application - Checking again for due payments after 1 second
[debug] application - Checking for due payments (CSV uploaded)
(after which, due payments are found & transacted)
The output on Heroku:
2018-11-18T11:48:01.247773+00:00 app[web.1]: [debug] application - Checking again for due payments after 1 second
(after which due payments are not transacted)
Is this just a limitation of the free tier of Heroku? Or is there something I can configure?
heroku playframework
There shouldn't be any limitation of the free tier that would prevent this. Do you know how thescheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?
– codefinger
Nov 19 '18 at 15:04
add a comment |
My Play v2.6 app uses scheduled tasks. These work when run locally, but never fire when deployed to Heroku.
There are previous questions related to this, but none have a relevant answer.
The logging when setting the task is printed, but the log messages when the task is executed does not appear. Also, the effect of the task being executed never happens.
The schedule is for 1 second in the future, so there's no chance for Heroku to be sleeping the app.
The source:
@Singleton
class PaymentProcessor @Inject()(repo: PaymentRepo,
config: Configuration,
system: ActorSystem) {
private val actor = system.actorOf(Props(new ActorDef()))
private implicit val ec: ExecutionContextExecutor = system.dispatcher
def checkForPayments(reason: String, after: FiniteDuration = 1.second): Unit = {
Logger.debug(s"Checking again for due payments after $after")
system.scheduler.scheduleOnce(after, actor, CheckForPayments(reason))
}
class ActorDef() extends Actor {
override def receive: Receive = {
case CheckForPayments(reason) =>
Logger.debug(s"Checking for due payments ($reason)")
// followed by logic to find and transact due payments
}
}
Here's the unabbreviated source.
The output locally:
[debug] application - Checking again for due payments after 1 second
[debug] application - Checking for due payments (CSV uploaded)
(after which, due payments are found & transacted)
The output on Heroku:
2018-11-18T11:48:01.247773+00:00 app[web.1]: [debug] application - Checking again for due payments after 1 second
(after which due payments are not transacted)
Is this just a limitation of the free tier of Heroku? Or is there something I can configure?
heroku playframework
My Play v2.6 app uses scheduled tasks. These work when run locally, but never fire when deployed to Heroku.
There are previous questions related to this, but none have a relevant answer.
The logging when setting the task is printed, but the log messages when the task is executed does not appear. Also, the effect of the task being executed never happens.
The schedule is for 1 second in the future, so there's no chance for Heroku to be sleeping the app.
The source:
@Singleton
class PaymentProcessor @Inject()(repo: PaymentRepo,
config: Configuration,
system: ActorSystem) {
private val actor = system.actorOf(Props(new ActorDef()))
private implicit val ec: ExecutionContextExecutor = system.dispatcher
def checkForPayments(reason: String, after: FiniteDuration = 1.second): Unit = {
Logger.debug(s"Checking again for due payments after $after")
system.scheduler.scheduleOnce(after, actor, CheckForPayments(reason))
}
class ActorDef() extends Actor {
override def receive: Receive = {
case CheckForPayments(reason) =>
Logger.debug(s"Checking for due payments ($reason)")
// followed by logic to find and transact due payments
}
}
Here's the unabbreviated source.
The output locally:
[debug] application - Checking again for due payments after 1 second
[debug] application - Checking for due payments (CSV uploaded)
(after which, due payments are found & transacted)
The output on Heroku:
2018-11-18T11:48:01.247773+00:00 app[web.1]: [debug] application - Checking again for due payments after 1 second
(after which due payments are not transacted)
Is this just a limitation of the free tier of Heroku? Or is there something I can configure?
heroku playframework
heroku playframework
asked Nov 18 '18 at 11:52
SynessoSynesso
20.1k27108166
20.1k27108166
There shouldn't be any limitation of the free tier that would prevent this. Do you know how thescheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?
– codefinger
Nov 19 '18 at 15:04
add a comment |
There shouldn't be any limitation of the free tier that would prevent this. Do you know how thescheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?
– codefinger
Nov 19 '18 at 15:04
There shouldn't be any limitation of the free tier that would prevent this. Do you know how the
scheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?– codefinger
Nov 19 '18 at 15:04
There shouldn't be any limitation of the free tier that would prevent this. Do you know how the
scheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?– codefinger
Nov 19 '18 at 15:04
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360547%2fplay-scheduled-async-tasks-dont-fire-on-heroku%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360547%2fplay-scheduled-async-tasks-dont-fire-on-heroku%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There shouldn't be any limitation of the free tier that would prevent this. Do you know how the
scheduleOnce
method works? Like, does it send an HTTP request, or does it create an event in-memory? Is it possible to trace through that call in some way?– codefinger
Nov 19 '18 at 15:04