cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CXF-2002) Server async jms transport needs dynamic mechanism to throttle message consumption
Date Wed, 06 May 2009 08:06:30 GMT

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

Freeman Fang edited comment on CXF-2002 at 5/6/09 1:06 AM:
-----------------------------------------------------------

just attach patch(created against 2.0.x branch) including several minor changes during the
discussion
NOTE, the BOGUS_MESSAGE_SELECTOR must be
BOGUS_MESSAGE_SELECTOR = "orgApacheCxfTransportsJmsContinuations='too-many'";
otherwise the selector would be ignored

      was (Author: ffang):
    just attach patch including several minor changes during the discussion
NOTE, the BOGUS_MESSAGE_SELECTOR must be
BOGUS_MESSAGE_SELECTOR = "orgApacheCxfTransportsJmsContinuations='too-many'";
otherwise the selector would be ignored
  
> 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
>         Attachments: CXF-2002.patch
>
>
> 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