Since PETALSESBCONT-190, the size of the message queue of the transporter is customizable. But each queue associated to its component has the same max size.
So to be more precise in the tuning and prevent memory consumption, the max size of the message queue should be customizable per components:
- parameter location: local container configuration (server.properties),
- parameter name: "petals.transport.queue.max-size.<component-jbi-id>",
- default value: value of the parameter "petals.transport.queue.max-size",
where "<component-jbi-id>" is the JBI identifier of the component
Improvement Request
New
Major
