Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.2.0
-
Fix Version/s: 5.3.0
-
Component/s: configuration
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Mathieu Carrolle [ mcarrolle ] | Christophe DENEUX [ cdeneux ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Summary | The message exchange processor pool is not reconfigured on hot-configuration | The message exchange processor pools are not correctly reconfigured on hot-configuration |
| Description | If the parameters {{processor-pool-size}} or {{processor-max-pool-size}} is hot-set, values are not propagated to the message exchange processor pool. Only the message exchange processor thread pool is reconfigured. |
If the parameters {{processor-pool-size}} or {{processor-max-pool-size}} is hot-set, values are not propagated to the message exchange processor pool. Only the message exchange processor thread pool is reconfigured.
Moreover, if {{processor-pool-size}} is increased, new core threads are not started. |
| Description |
If the parameters {{processor-pool-size}} or {{processor-max-pool-size}} is hot-set, values are not propagated to the message exchange processor pool. Only the message exchange processor thread pool is reconfigured.
Moreover, if {{processor-pool-size}} is increased, new core threads are not started. |
If the parameters {{processor-pool-size}} or {{processor-max-pool-size}} is hot-set, values are not propagated to the message exchange processor pool. Only the message exchange processor thread pool is reconfigured.
Moreover, if {{processor-pool-size}} is increased, new core threads should be started. |
| Link |
This issue depends on |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.3.0 [ 10338 ] | |
| Resolution | Fixed [ 1 ] |