Petals SE Activiti

The async job executor should be tunnable

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0.0
  • Fix Version/s: 1.0.1, 1.1.0
  • Component/s: Configuration
  • Security Level: Public
  • Description:
    Hide

    The Petals SE Activiti provides a parameter to enable or disable the async job executor, but we can't set the parameters of this async job executor.

    The following parameters are described in the Activiti engine documentation. Please reuse the same names and the same default values:

    Parameter name Default value Description
    corePoolSize 2 The minimal number of threads that are kept alive in the thread pool for job execution.
    maxPoolSize 10 The maximum number of threads that are kept alive in the thread pool for job execution.
    keepAliveTime 5000 The time (in milliseconds) a thread used for job execution must be kept alive before it is destroyed. Default setting is 0. Having a non-default setting of 0 takes resources, but in the case of many job executions it avoids creating new threads all the time.
    queueSize 100 The size of the queue on which jobs to be executed are placed.
    maxTimerJobsPerAcquisition 1 The number of timer jobs that are fetched from the database in one query.
    maxAsyncJobsDuePerAcquisition 1 The number of asynchronous jobs due that are fetched from the database in one query.
    defaultAsyncJobAcquireWaitTimeInMillis 10000 The time in milliseconds between asynchronous job due queries being executed.
    defaultTimerJobAcquireWaitTimeInMillis 10000 The time in milliseconds between timer job queries being executed.
    timerLockTimeInMillis 300000 The time in milliseconds that a timer job is locked before being retried again. The Activiti Engine considers the timer job to have failed after this period of time and will retry.
    asyncJobLockTimeInMillis 300000 The time in milliseconds that an asynchronous job is locked before being retried again. The Activiti Engine considers the asynchronous job to have failed after this period of time and will retry.
    Show
    The Petals SE Activiti provides a parameter to enable or disable the async job executor, but we can't set the parameters of this async job executor. The following parameters are described in the Activiti engine documentation. Please reuse the same names and the same default values:
    Parameter name Default value Description
    corePoolSize 2 The minimal number of threads that are kept alive in the thread pool for job execution.
    maxPoolSize 10 The maximum number of threads that are kept alive in the thread pool for job execution.
    keepAliveTime 5000 The time (in milliseconds) a thread used for job execution must be kept alive before it is destroyed. Default setting is 0. Having a non-default setting of 0 takes resources, but in the case of many job executions it avoids creating new threads all the time.
    queueSize 100 The size of the queue on which jobs to be executed are placed.
    maxTimerJobsPerAcquisition 1 The number of timer jobs that are fetched from the database in one query.
    maxAsyncJobsDuePerAcquisition 1 The number of asynchronous jobs due that are fetched from the database in one query.
    defaultAsyncJobAcquireWaitTimeInMillis 10000 The time in milliseconds between asynchronous job due queries being executed.
    defaultTimerJobAcquireWaitTimeInMillis 10000 The time in milliseconds between timer job queries being executed.
    timerLockTimeInMillis 300000 The time in milliseconds that a timer job is locked before being retried again. The Activiti Engine considers the timer job to have failed after this period of time and will retry.
    asyncJobLockTimeInMillis 300000 The time in milliseconds that an asynchronous job is locked before being retried again. The Activiti Engine considers the asynchronous job to have failed after this period of time and will retry.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 10 Dec 2015 - 12:50:35 +0100
Field Original Value New Value
Fix Version/s 1.0.1 [ 10578 ]
Priority Major [ 3 ]
Component/s Configuration [ 10376 ]
Christophe DENEUX made changes - Fri, 11 Dec 2015 - 12:14:13 +0100
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Fri, 11 Dec 2015 - 12:14:24 +0100
Priority Major [ 3 ] Minor [ 4 ]
Christophe DENEUX made changes - Fri, 11 Dec 2015 - 12:14:26 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Fri, 11 Dec 2015 - 12:14:48 +0100

Configuration parameters added in branch 'master'

Show
Christophe DENEUX added a comment - Fri, 11 Dec 2015 - 12:14:48 +0100 Configuration parameters added in branch 'master'
Christophe DENEUX made changes - Fri, 11 Dec 2015 - 12:14:48 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 26 Jan 2017 - 16:37:55 +0100
Link This issue depends on PETALSSEACTIVITI-31 [ PETALSSEACTIVITI-31 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:38:54 +0100

Reopen because the queue size parameter is not available at installation configuration MBean level

Show
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:38:54 +0100 Reopen because the queue size parameter is not available at installation configuration MBean level
Christophe DENEUX made changes - Thu, 26 Jan 2017 - 16:38:54 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 26 Jan 2017 - 16:38:57 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:39:45 +0100

The parameter about queue size is now available at installation configuration MBean level (see PETALSSEACTIVITI-31)

Show
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:39:45 +0100 The parameter about queue size is now available at installation configuration MBean level (see PETALSSEACTIVITI-31)
Christophe DENEUX made changes - Thu, 26 Jan 2017 - 16:39:45 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.1.0 [ 10692 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:41:05 +0100

Reopened because several parameters are not available at installation configuration MBean level:

  • maxTimerJobsPerAcquisition
  • maxAsyncJobsDuePerAcquisition
  • defaultAsyncJobAcquireWaitTimeInMillis
  • defaultTimerJobAcquireWaitTimeInMillis
  • timerLockTimeInMillis
  • asyncJobLockTimeInMillis
Show
Christophe DENEUX added a comment - Thu, 26 Jan 2017 - 16:41:05 +0100 Reopened because several parameters are not available at installation configuration MBean level:
  • maxTimerJobsPerAcquisition
  • maxAsyncJobsDuePerAcquisition
  • defaultAsyncJobAcquireWaitTimeInMillis
  • defaultTimerJobAcquireWaitTimeInMillis
  • timerLockTimeInMillis
  • asyncJobLockTimeInMillis
Christophe DENEUX made changes - Thu, 26 Jan 2017 - 16:41:05 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Fri, 27 Jan 2017 - 09:52:46 +0100
Link This issue depends on PETALSSEACTIVITI-33 [ PETALSSEACTIVITI-33 ]
Christophe DENEUX made changes - Mon, 30 Jan 2017 - 11:23:09 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Mon, 30 Jan 2017 - 11:32:59 +0100

Fix in trunk. 'engine-job-executor-async-job-due-acquire-wait-time' was renamed into 'engine-job-executor-async-job-acquire-wait-time'.

Show
Christophe DENEUX added a comment - Mon, 30 Jan 2017 - 11:32:59 +0100 Fix in trunk. 'engine-job-executor-async-job-due-acquire-wait-time' was renamed into 'engine-job-executor-async-job-acquire-wait-time'.
Christophe DENEUX made changes - Mon, 30 Jan 2017 - 11:32:59 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
23h 24m
1
Christophe DENEUX
Fri, 11 Dec 2015 - 12:14:13 +0100
Open Open In Progress In Progress
13s
1
Christophe DENEUX
Fri, 11 Dec 2015 - 12:14:26 +0100
In Progress In Progress Resolved Resolved
22s
1
Christophe DENEUX
Fri, 11 Dec 2015 - 12:14:48 +0100
Resolved Resolved Open Open
412d 4h 24m
1
Christophe DENEUX
Thu, 26 Jan 2017 - 16:38:54 +0100
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Thu, 26 Jan 2017 - 16:38:57 +0100
In Progress In Progress Resolved Resolved
48s
1
Christophe DENEUX
Thu, 26 Jan 2017 - 16:39:45 +0100
Resolved Resolved Open Open
1m 20s
1
Christophe DENEUX
Thu, 26 Jan 2017 - 16:41:05 +0100
Open Open In Progress In Progress
3d 18h 42m
1
Christophe DENEUX
Mon, 30 Jan 2017 - 11:23:09 +0100
In Progress In Progress Resolved Resolved
9m 50s
1
Christophe DENEUX
Mon, 30 Jan 2017 - 11:32:59 +0100

People

Dates

  • Created:
    Thu, 10 Dec 2015 - 12:49:52 +0100
    Updated:
    Mon, 30 Jan 2017 - 11:32:59 +0100
    Resolved:
    Mon, 30 Jan 2017 - 11:32:59 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.