[
https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699366#action_12699366
]
Christian Schneider commented on CXF-2002:
------------------------------------------
Hi Sergey,
I must confess I still do not get the idea behind continuations for JMS. If you
want to throttle the message consumption then you use only one or few
consumers. They will then only consume as many messages as they can work on.
When combined with a syncronous task executor this should throttle message
consumption quite effectively. (See
http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html).
Technically the configuration property you talked of can be added to
JMSConfiguration as well as to the WSDL of course.
Greetings,
Christian
> 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
> Fix For: 2.2.1
>
>
> 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.
