Petals CDK

If no more message exchange processor thread is available, new incoming message exchange should be enqueued instead of to be rejected

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 5.1.3, 5.2.0
Fix Version/s: 5.1.4, 5.3.0
Component/s: runtime
Security Level: Public

Description:

Hide

To accept bursts of message exchanges (for example generated by diffusion/aggregation component), new incoming message exchange should be enqueued instead of to be rejected.

~~To prevent resources consumption, the queue size can be customized through the component parameter 'processor-queue-size'.~~ ~~This parameter can be hot-set.~~

Show
To accept bursts of message exchanges (for example generated by diffusion/aggregation component), new incoming message exchange should be enqueued instead of to be rejected. ~~To prevent resources consumption, the queue size can be customized through the component parameter 'processor-queue-size'.~~ ~~This parameter can be hot-set.~~

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSCDK-100~~ Utility of 2 maps of AsyncMessageManager must be reviewed.
~~PETALSESBCONT-190~~ The size of the message queue of the transporter should be customizable
~~PETALSESBCONT-191~~ When the message queue of transporter is full, the enqueuing should wait a moment before to fail.

Duplicate

This issue is duplicated by:
~~PETALSCDK-89~~ If all JBI message exchange processors are running, additional requests are rejected

Activity

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 19 Apr 2012 - 17:29:28 +0200

Updated:

Thu, 31 May 2012 - 12:50:54 +0200

Resolved:

Thu, 31 May 2012 - 12:50:54 +0200