Petals ESB Container

The size of the message queue of the transporter should be customizable

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
To prevent memory consumption of component running few requests, or adjust it correctly for components running big burst of requests, the size of the message queue of the transporter should be customizable:

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

parameter name: "petals.transport.queue.max-size",

default value: 10000 (existing hard-coded value).
Show
To prevent memory consumption of component running few requests, or adjust it correctly for components running big burst of requests, the size of the message queue of the transporter should be customizable:

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

parameter name: "petals.transport.queue.max-size",

default value: 10000 (existing hard-coded value).

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

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 10 May 2012 - 11:06:42 +0200

Updated:

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

Resolved:

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