Petals ESB Container

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

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major 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
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 10 May 2012 - 11:07:19 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Component/s Transporter [ 10062 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 11:07:21 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 11:15:16 +0200
Link This issue blocks PETALSCDK-91 [ PETALSCDK-91 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 11:15:51 +0200
Description 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 loaction: local container configuration (server.properties),
- paranmeter name: "petals.transport.queue.max-size",
- default value: 10000 (existing hard-coded value). 		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).
Christophe DENEUX made changes - Thu, 10 May 2012 - 11:56:48 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 3.3.0 [ 10334 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 16:26:54 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 16:26:57 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 10 May 2012 - 16:27:15 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 3.1.4 [ 10255 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Tue, 12 Mar 2013 - 08:34:37 +0100
Component/s Configuration [ 10257 ]

People

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
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.