Petals CDK

The parameter 'processorMaxPoolSize' is not used to size the JBI message workers pool

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 4.0.10
  • Fix Version/s: 5.1.2
  • Component/s: runtime
  • Security Level: Public
  • Description:
    Hide

    The thread pool of JBI message workers is sized with:

    • core pool size: the value of the parameter 'processorPoolSoze',
    • max pool size: 255 (hard coded value),
    • keep alive time: 60s (hard coded value),
    • work queue size: 1024 (hard coded value)

    The max pool size should be customizable through the existing parameter 'processorMaxPoolSize'

    Show
    The thread pool of JBI message workers is sized with:
    • core pool size: the value of the parameter 'processorPoolSoze',
    • max pool size: 255 (hard coded value),
    • keep alive time: 60s (hard coded value),
    • work queue size: 1024 (hard coded value)
    The max pool size should be customizable through the existing parameter 'processorMaxPoolSize'
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 1 Aug 2011 - 10:14:02 +0200

Already fixed in CDK trunk.

Show
Christophe DENEUX added a comment - Mon, 1 Aug 2011 - 10:14:02 +0200 Already fixed in CDK trunk.

People

Dates

  • Created:
    Mon, 1 Aug 2011 - 09:58:24 +0200
    Updated:
    Mon, 1 Aug 2011 - 10:20:56 +0200
    Resolved:
    Mon, 1 Aug 2011 - 10:14:02 +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.