Details
-
Type:
Improvement Request
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.6.0
-
Fix Version/s: None
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | ||||||
|---|---|---|---|---|---|---|
|
|
|||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Link | This issue depends on PETALSESBCONT-339 [ PETALSESBCONT-339 ] |
| Link |
This issue depends on |
| Description |
Currently, when there is no more threads available in the exchange processor, exchanges are sent back in error.
There should be some way to configure this more finely, with various strategies, at the CDK level (either component or SU... to be discussed). |
Currently, when there is no more threads available in the exchange processor, exchanges are sent back in error (see There should be some way to configure this more finely, with various strategies, at the CDK level (either component or SU... to be discussed). |
| Link | This issue blocks PETALSDISTRIB-146 [ PETALSDISTRIB-146 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
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.