#551 ✓wontfix
Ahmet Alp Balkan

Jobs are not working in GAE plugin. A bug?

Reported by Ahmet Alp Balkan | January 19th, 2011 @ 07:10 PM

When you integrate gae-1.4 plugin and siena-1.3 to your Hello World application and create a DummyJob extends Job, and set it to @OnApplicationStart and print out something to the console in doJob() method, it does not work at all. I have tried with @On with a every minute cronjob. It does not even throw an exception when I describe an improper cron interval string in @On.

Maybe it is all about using GAE, however it is not stated that @Jobs won't work in GAE plugin documentation.

Comments and changes to this ticket

  • Jean-Philippe Briend

    Jean-Philippe Briend February 2nd, 2011 @ 10:22 AM

    Play! Jobs are not working in GAE.
    I think I read it on the Groups.

    Check GAE documentation to use its functionalities (TaskQueues, etc...).

  • Erwan Loisant

    Erwan Loisant June 9th, 2011 @ 12:45 PM

    • State changed from “new” to “wontfix”

    Indeed, you need to use GAE's cron functionality.

  • Ahmet Alp Balkan

    Ahmet Alp Balkan June 9th, 2011 @ 04:12 PM

    I think there must be an exception thrown if GAE plugin is in use and at the same time Job is used. There must be a few people out there like me thinking of Jobs can work on GAE.

    Actually when I posted this issue to the Google Group, someone implemented a prototype that redirects Jobs to GAE TaskQueue. Maybe it can be officially implemented in GAE plugin. Just an idea.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.