Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <451617492.1239815294899.JavaMail.jira@brutus>
Date: Wed, 15 Apr 2009 10:08:14 -0700 (PDT)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Commented: (CXF-2002) Server async jms transport needs
 dynamic mechanism to throttle message consumption
In-Reply-To: <1839152316.1232770559952.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Hmm... 

What I've actually found is that Spring DefaultMessageListenerContainer does not allow a 0 value for concurrentConsumers. 1 is a minimum value.

Thus the only option there seems to try to limit the flow of messages by setting both concurrentConsumers and maxConcurrentConsumers to '1' - which is what the default values are.

Guys, am I missing something may be ? Ron - do you use set the value of 'concurrentConsumers' in production to the one which is bigger than 1 ? If so then limiting the flow might do the trick, otherwise I'm not sure what else can be done

Thoughts ?

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