[
https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667084#action_12667084
]
Christian Schneider commented on CXF-2002:
------------------------------------------
Hi Ron,
I was not really following the efforts of implementing Continuations for jms.
But as far as I understand from Sergey´s blog continuations provide a solution
for something jms does in any case. Async communication is the basis of jms.
You send a message to a queue and listen for a reply on a another queue. In
http a client has to hold a thread open that actively waits for a response. In
jms the client does not even have to be online. The server chooses when to
retrieve the message from the request queue and when it is finished it sends
the response back.
So I really wonder if continuations make sense for jms. What do you think? I
will try to discuss this with sergey.
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: Christian Schneider
> Fix For: 2.2
>
>
> 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.
