[
https://issues.apache.org/jira/browse/CXF-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702274#action_12702274
]
Freeman Fang edited comment on CXF-2002 at 4/24/09 12:52 AM:
-------------------------------------------------------------
Hi Sergey,
After change to orgApacheCxfTransportsJmsContinuations=too-many, the
javax.jms.InvalidSelectorException just gone.
I'm still running the test more times to ensure the message lost problem get
fixed, since the message lost problem not happen to me every time before, need
more test now, :-)
Will get you posted.
Thanks again for your help
Freeman
was (Author: ffang):
Hi Sergey,
After change to orgApacheCxfTransportsJmsContinuations=too-many, the
javax.jms.InvalidSelectorException just gone.
I'm still running the test more times to ensure the message lost problem get
fixed.
Will get you posted.
Thanks a lot for your help
Freeman
> 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
>
> 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.
