Quartz Plugin

concurrent property, not working

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 0.2
  • Fix Version/s: 0.3
  • Component/s: None
  • Labels:
    None
  • Environment:
    grails 1.0.2, java 1.6.0_02, linux

Description

def concurrent = false, causes job's not to get executed..

class ConcTestJob {

def timeout = 1000l
def concurrent = false

def execute() { int me = ++counter; println(">> $me") Thread.sleep(2500) println("<< $me") }

private static int counter;
}

  • with this code, the job is never executed
  • changing to "concurrent = true", causes i to run, concurrenlty
  • chaning to "def synchronized execute() {.." causes the desired behaviour

Issue Links

Activity

Hide
Sergey Nebolsin added a comment -

Looks like early job execution appears again (first job execution is started before application completes its startup process -> exception -> job hangs up). Adding def startDelay = 5000 seems like a workaround for the problem.

I'll look deeper into that.

Show
Sergey Nebolsin added a comment - Looks like early job execution appears again (first job execution is started before application completes its startup process -> exception -> job hangs up). Adding def startDelay = 5000 seems like a workaround for the problem. I'll look deeper into that.
Hide
Lars Hvile added a comment -

I don't think that was the problem, the "real" job i was using when i found the bug has a startDelay of 30000 or more..

Show
Lars Hvile added a comment - I don't think that was the problem, the "real" job i was using when i found the bug has a startDelay of 30000 or more..
Hide
Sergey Nebolsin added a comment -

Hmm.. That's strange. Are you using 0.2 version of the plugin or 0.3-SNAPSHOT? I cannot reproduce the problem with the latest 0.3-SNAPSHOT and startDelay parameter. Without startDelay parameter I encounter the same behavior as you described.

Anyway, I'll return to this issue when I fix GRAILSPLUGINS-359.

Show
Sergey Nebolsin added a comment - Hmm.. That's strange. Are you using 0.2 version of the plugin or 0.3-SNAPSHOT? I cannot reproduce the problem with the latest 0.3-SNAPSHOT and startDelay parameter. Without startDelay parameter I encounter the same behavior as you described. Anyway, I'll return to this issue when I fix GRAILSPLUGINS-359.
Hide
Lars Hvile added a comment -

I'm using 0.2

Show
Lars Hvile added a comment - I'm using 0.2
Hide
Sergey Nebolsin added a comment -

Lars, I've just uploaded new snapshot version of the plugin with several bugfixes and improvements. Could you give it a try and confirm if the issue still exists? And if it's still valid, could you please provide a reproducible example since I cannot reproduce this issue in my environment (I'm trying your exact code).

I really want to sort out this issue before 0.3 release of the plugin which is planned for this week (or this weekend possible).

Show
Sergey Nebolsin added a comment - Lars, I've just uploaded new snapshot version of the plugin with several bugfixes and improvements. Could you give it a try and confirm if the issue still exists? And if it's still valid, could you please provide a reproducible example since I cannot reproduce this issue in my environment (I'm trying your exact code). I really want to sort out this issue before 0.3 release of the plugin which is planned for this week (or this weekend possible).
Hide
Lars Hvile added a comment -

Ok, just tested with the 0.3 snapshot, and I can confirm that it's working.. both with and without startDelay, nice work =)

Show
Lars Hvile added a comment - Ok, just tested with the 0.3 snapshot, and I can confirm that it's working.. both with and without startDelay, nice work =)
Hide
Sergey Nebolsin added a comment -

Great, so I'm closing this one. Thanks for your feedback.

Show
Sergey Nebolsin added a comment - Great, so I'm closing this one. Thanks for your feedback.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: