Announcement Announcement Module
Collapse
No announcement yet.
Stopping jobs "via the database" Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stopping jobs "via the database"

    The docs mention in section '2.4 Meta Data Access Improvements' that
    "It is also worth noting that Jobs can now be stopped via the database..."
    Having noted that - I'd be interested to know what it means. I mean understand - not assume.

    However, this is what I assume. That one should update the database (via the JobRepository) using the JobOperator interface. I see JobOperator has a handy looking stop(executionId) method.

    Also note the (Simple)JobService supports stop and stopAll calls.

    I know it sounds obvious but just double checking that I've interpreted this correctly.

    TIA,
    David.
    Last edited by dvb123; Jan 27th, 2012, 07:54 PM.

  • #2
    FWIW. I resolved this by using the SimpleJobService.

    Your mileage may vary.

    Comment

    Working...
    X