Petals ESB Container

When the message queue of transporter is full, the enqueuing should wait a moment before to fail.

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

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 3.1.3, 4.0.0
Fix Version/s: 3.1.4, 4.1.0
Component/s: Configuration, Transporter
Security Level: Public

Description:
Hide
In case of a burst of requests, if the message queue is full, a new request is rejected, whereas if the enqueuing (in fact the message sender) was blocking a little moment, space would be freed in the queue and the request could be executed.
The little moment to wait will be customizable:

parameter location: local container configuration (server.properties),

parameter name: "petals.transport.queue.offering.timeout",

default value: 2500 milliseconds.
Show
In case of a burst of requests, if the message queue is full, a new request is rejected, whereas if the enqueuing (in fact the message sender) was blocking a little moment, space would be freed in the queue and the request could be executed. The little moment to wait will be customizable:

parameter location: local container configuration (server.properties),

parameter name: "petals.transport.queue.offering.timeout",

default value: 2500 milliseconds.

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSCDK-91~~ If no more message exchange processor thread is available, new incoming message exchange should be enqueued instead of to be rejected

Activity

Ascending order - Click to sort in descending order

No work has yet been logged on this issue.

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 10 May 2012 - 11:14:32 +0200

Updated:

Tue, 12 Mar 2013 - 08:34:54 +0100

Resolved:

Thu, 10 May 2012 - 16:28:14 +0200