[
https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667124#action_12667124
]
Ron Gavlin commented on CXF-2002:
---------------------------------
Hi Christian,
I believe the CXFContinuation is a transport-agnostic mechanism for de-coupling
the request thread from the worker-thread in the CXF server. Since JMS is
inherently asynchronous, I believe the CXFContinuation mechanism for JMS is
quite lightweight. When CXF is embedded in frameworks like SMX that tend to
support long-running tasks, the CxfContinuation is a convenient integration
point. I believe the smx-cxf-bc consumer leverages this mechanism for its async
JMS support.
/Ron
> 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.
