[ 
https://issues.apache.org/jira/browse/CXF-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-8105.
-------------------------------
    Fix Version/s: 3.3.4
                   3.2.11
                   3.4.0
       Resolution: Fixed

> introduce a property for JMS transport client to decide reset JMS connection 
> or not when client timeout
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-8105
>                 URL: https://issues.apache.org/jira/browse/CXF-8105
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>            Priority: Major
>             Fix For: 3.4.0, 3.2.11, 3.3.4
>
>
> When using JMS transport, the client can encounter receive timeout from time 
> to time. This timeout could be caused by the serious problem in broker(like 
> crash or restart), in which case a JMS connection reset is required. Or the 
> timeout could be just a request need a longer time to process it on the 
> server side, in this case a JMS connection reset is a overkill.
> We should introduce a property to control this behavior, let end users to 
> decide which scenario fits their requirement.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to