[
https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706405#action_12706405
]
Sergey Beryozkin commented on CXF-2002:
---------------------------------------
Hi Freeman - thanks for submitting these changes in a single patch...They're
now in 2.0.x, 2.1.x, trunk.
Hi Ron : can you please give it a try now in your own production environment ?
I won't close this JIRA at the moment - please get back and let us know if the
provider fix works for you and if you reckon it is worth investigating the
possibility of restarting DLMC.
In meantime I'll investigate the apparent leakage Freeman observed.
thanks, Sergey
> Server async jms transport needs dynamic mechanism to throttle message
> consumption
> ----------------------------------------------------------------------------------
>
> Key: CXF-2002
> URL: https://issues.apache.org/jira/browse/CXF-2002
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.0.9, 2.1.3, 2.0.10
> Reporter: Ron Gavlin
> Assignee: Sergey Beryozkin
> Attachments: CXF-2002.patch
>
>
> Currently, the server-side async jms transport has no mechanism to throttle
> consumption of incoming messages. This becomes problematic in scenarios where
> a large backlog of messages exists on the input queue. In this case, it is
> likely that the cxf server will overload its internal work item queues
> resulting in problems. A dynamic throttling mechanism on the async jms server
> is required to avoid this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
