#1027 new
Laurent Ho

Adding Jobs with different priorities (by using PriorityBlockingQueue in JobsPlugin)

Reported by Laurent Ho | August 10th, 2011 @ 08:26 AM

Hi
I wonder how many people could use this feature, because Play is great for simple Batch applications, but lacks some 'high end' features like this task prioritization (and another highly useful one would be 'jobs persistence' plus a management-backend for running/finished jobs.. maybe there's a plugin for this??).
We now quickly need a Jobs prioritization feature because our application is handling hundreds of jobs each day, and some of these jobs should not be allowed to wait for hours before they can get executed..the client cannot wait;)

The easiest Way to achieve this 'task prioritization' (without adding any new external frameworks!) seems to be by using a PriorityBlockingQueue in combination with the already used ThreadPoolExecutor, as shown here:
http://stackoverflow.com/questions/807223/how-do-i-implement-task-p...
http://stackoverflow.com/questions/3545623/how-to-implement-priorit...

Another easier solution (just enough for us, but no real priority support) would be:
http://binkley.blogspot.com/2009/04/jumping-work-queue-in-executor....

And finally using a 'real' library like quartz might me a better option, but would such a patch have any chance to be adopted in the main branch?!

We are open for other ideas, specially if they have higher chances to get integrated directly in play!
And for existing patches of course!

Thanks a lot,
Laurent

No comments found

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.

People watching this ticket

Pages