cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2002) Server async jms transport needs dynamic mechanism to throttle message consumption
Date Tue, 27 Jan 2009 11:38:59 GMT

    [ https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667649#action_12667649
] 

Sergey Beryozkin commented on CXF-2002:
---------------------------------------

Hi Christian

We discussed this issue with Ron on #cxf.
It seems that what Ron suggested is doable. JMS Continuation is really a light weight way
to decouple a (JMS request) thread from an (application) worker thread, please see 

http://svn.apache.org/repos/asf/cxf/trunk/rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/continuations/,
JMSDestination creates a new continuation instance per in message.

users can also get (Jetty) HTTP and JMS requests and suspend them using the same api.

JMSContinuationProvider  adds new continuations to a (concurrent) list, while JMSContinuation
removes itself when it expires or get resumed. 

I was thinking that if we passed a JMSDestination.listener and JMSConfiguration to JMSContinuationProvider
and  JMSContinuation, then we'd be able to set a number of concurrentConsumers on a listener
as appropriate

Does it make sense ? thanks...





> 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.


Mime
View raw message