Petals SE BPEL

Improve the configuration of the max number of concurrent BPEL process instances

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.1
  • Fix Version/s: Vnext
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The max number of concurrent BPEL process instances can be set at SU level with the parameter bpel-engine:poolsize.

    This parameter is not intuitive. It should be better to:

    • introduce, at component level, a new parameter limiting the max number of concurrent process instances of ONE BPEL sheet. Default value is value of the max number of JBI message processors
    • keep this parameter. By default (no value defined), the value defined at component level is used.
    Show
    The max number of concurrent BPEL process instances can be set at SU level with the parameter bpel-engine:poolsize. This parameter is not intuitive. It should be better to:
    • introduce, at component level, a new parameter limiting the max number of concurrent process instances of ONE BPEL sheet. Default value is value of the max number of JBI message processors
    • keep this parameter. By default (no value defined), the value defined at component level is used.
  • Environment:
    -

People

Dates

  • Created:
    Wed, 21 Mar 2012 - 12:05:59 +0100
    Updated:
    Tue, 26 Jun 2012 - 11:20:43 +0200
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.