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

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

Hi Freeman :

> And I just found that JMSDestination.activate() method will hang

This is in your first comment : I'm not seeing how it is related to this issue 
as the configuration does not include maxSuspendedContinuations & cacheLevel.

> javax.jms.InvalidSelectorException: 
> org.apache.cxf.transports.jms.continuations=too-many 

it's a second issue...The value is broken, there should be no '.'s, though I 
don't remember seeing this exception during the (in-process) system test - but 
either way I'll fix it...

can you please give me a favor and do a quick local build for CXF JMS transport 
and update org.apache.cxf.transports.jms.continuations=too-many to

orgApacheCxfTransportsJmsContinuations=too-many

in org.apache.cxf.transports.jms.continuations.JMSContinuation.java ?

and see if the messages are not lost any more, before I start pushing this fix 
to the trunk/2.1.x/2.0.x ?

thanks, Sergey

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

Reply via email to