Petals CDK

The message exchange processor pools are not correctly reconfigured on hot-configuration

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.2.0
  • Fix Version/s: 5.3.0
  • Component/s: configuration
  • Security Level: Public
  • Description:
    Hide

    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.

    Show
    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.
  • Environment:
    -

Issue Links

Activity

Christophe DENEUX made changes - Fri, 20 Apr 2012 - 18:35:22 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Mathieu Carrolle [ mcarrolle ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Fri, 20 Apr 2012 - 18:35:24 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Fri, 20 Apr 2012 - 18:55:02 +0200
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.
Christophe DENEUX made changes - Fri, 20 Apr 2012 - 18:55:46 +0200
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.
Hide
Christophe DENEUX added a comment - Mon, 23 Apr 2012 - 09:47:10 +0200 - edited

The message exchange processor thread pool is not correctly reduced when decreasing the core pool size because of a JVM's bug --> PETALSCDK-94

Show
Christophe DENEUX added a comment - Mon, 23 Apr 2012 - 09:47:10 +0200 - edited The message exchange processor thread pool is not correctly reduced when decreasing the core pool size because of a JVM's bug --> PETALSCDK-94
Christophe DENEUX made changes - Mon, 23 Apr 2012 - 09:47:10 +0200
Link This issue depends on PETALSCDK-94 [ PETALSCDK-94 ]
Hide
Christophe DENEUX added a comment - Mon, 23 Apr 2012 - 10:25:11 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Mon, 23 Apr 2012 - 10:25:11 +0200 Fixed in trunk
Christophe DENEUX made changes - Mon, 23 Apr 2012 - 10:25:11 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.3.0 [ 10338 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
8s
1
Christophe DENEUX
Fri, 20 Apr 2012 - 18:35:22 +0200
Open Open In Progress In Progress
2s
1
Christophe DENEUX
Fri, 20 Apr 2012 - 18:35:24 +0200
In Progress In Progress Resolved Resolved
2d 15h 49m
1
Christophe DENEUX
Mon, 23 Apr 2012 - 10:25:11 +0200



People

Dates

  • Created:
    Fri, 20 Apr 2012 - 18:35:14 +0200
    Updated:
    Mon, 23 Apr 2012 - 10:25:11 +0200
    Resolved:
    Mon, 23 Apr 2012 - 10:25:10 +0200