GrailsFlow

Add possibility to disable process engine jobs (NodeActivatorJob, DueDateJob) in configuration.

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.0
  • Fix Version/s: 1.0.12
  • Component/s: None
  • Labels:
    None
  • Request Controller:
    Please Select
  • External Supervisor:
    Please select
  • Executing Programmer:
    Please select
  • Ext Project Id:
    JCGFW-01

Description

Sometimes it is necessary to disable Grailsflow system jobs running(NodeActivatorJob, DueDateJob). Currently it is possible to stop job execution through 'Scheduler Details' controller, but when the user restart application or server, the job starts execution again. We need possibility to configure default behavior for system jobs before application starts.

Activity

Hide
Antonicheva, July added a comment - 14/Feb/12 8:51 AM - edited

It is possible to disable Grailsflow Jobs (NodeActivatorJob, DueDateJob) before starting application by configuring special options in Config.groovy:

grailsflow.scheduler.nodeActivator.autoStart = false // disable auto starting for NodeActivator Engine Job
grailsflow.scheduler.nodeDueDate.autoStart = false // disable auto starting for DueDate Job

Or it's possible to set these options in files that are specified in grails.config.locations path of your application.

Show
Antonicheva, July added a comment - 14/Feb/12 8:51 AM - edited It is possible to disable Grailsflow Jobs (NodeActivatorJob, DueDateJob) before starting application by configuring special options in Config.groovy:
grailsflow.scheduler.nodeActivator.autoStart = false // disable auto starting for NodeActivator Engine Job grailsflow.scheduler.nodeDueDate.autoStart = false // disable auto starting for DueDate Job
Or it's possible to set these options in files that are specified in grails.config.locations path of your application.

People

Vote (0)
Watch (0)

Dates

  • Created:
    25/Nov/11 11:08 AM
    Updated:
    24/Feb/12 8:46 AM
    Resolved:
    24/Feb/12 8:46 AM