cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Gavlin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2002) Server async jms transport needs dynamic mechanism to throttle message consumption
Date Wed, 15 Apr 2009 20:23:15 GMT

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

Ron Gavlin commented on CXF-2002:
---------------------------------

Hi Sergey,

Yes, it appears that the minimum value for concurrentConsumers is 1.

What would you think about setting a bogus selector on the DefaultMessageListenerContainer
to suspend message consumption? That appears to be the technique used to implement JMS-based
throttling in the new SMX4 Cluster Endpoint (see http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/jbi/cluster/src/main/java/org/apache/servicemix/jbi/cluster/ClusterEndpoint.java?rev=741598&view=auto).
In order to resume message consumption, the original selector (if any) would be restored.

Thoughts?

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


Mime
View raw message