Details
-
Type:
Improvement Request
-
Status:
New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.1
-
Fix Version/s: Vnext
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Marc Jambert [ mjambert ] | |
| Fix Version/s | 1.2.0 [ 10344 ] | |
| Priority | Major [ 3 ] |
| Description |
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. 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. |
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. |
| Fix Version/s | Vnext [ 10366 ] | |
| Fix Version/s | 1.2.0 [ 10344 ] |