Petals CDK

Handle capacity saturation of exchange processor with various strategies

Details

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

    Currently, when there is no more threads available in the exchange processor, exchanges are sent back in error (see PETALSCDK-135).

    There should be some way to configure this more finely, with various strategies, at the CDK level (either component or SU... to be discussed).

    Show
    Currently, when there is no more threads available in the exchange processor, exchanges are sent back in error (see PETALSCDK-135). There should be some way to configure this more finely, with various strategies, at the CDK level (either component or SU... to be discussed).
  • Environment:
    -

Issue Links

Depends

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Victor NOËL added a comment - Wed, 14 Sep 2016 - 10:01:45 +0200

This is linked to PETALSESBCONT-339 (it is about taking care of the memory consumption of the kernel and DeliveryChannel as their size will grow if the messages are not dropped nor processed) if we want to never drop exchanges.

Show
Victor NOËL added a comment - Wed, 14 Sep 2016 - 10:01:45 +0200 This is linked to PETALSESBCONT-339 (it is about taking care of the memory consumption of the kernel and DeliveryChannel as their size will grow if the messages are not dropped nor processed) if we want to never drop exchanges.

People

Dates

  • Created:
    Wed, 14 Sep 2016 - 09:59:27 +0200
    Updated:
    Wed, 14 Sep 2016 - 10:03:33 +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.