[
https://issues.apache.org/jira/browse/CXF-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-5382.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Assignee: Daniel Kulp
This is pretty much working as designed. When you call the getConduit() and
similar API's you are getting a specific conduit to configure. If some event
(such as failover) occurs, a new conduit is created and reconfigured from the
various configuration sources (blueprint/spring/etc...).
If you need setting set from API's (instead of configuration), you may need a
specific subclass of the FailoverFeature or maybe ConduitSelector.
> Clustering features: receiveTimeOut and connectTimeOut are reset to default
> when changing conduits on the fly
> -------------------------------------------------------------------------------------------------------------
>
> Key: CXF-5382
> URL: https://issues.apache.org/jira/browse/CXF-5382
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, JAX-WS Runtime
> Affects Versions: 2.7.7
> Reporter: Jacek Obarymski
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> This concerns clustering features of JAX-WS or JAX-RS client when conduit
> gets chaned on the fly.
> There's an option of setting receiveTimeout on conduit, e.g.
> Book proxy = JAXRSClientFactory.create("http://books";, Book.class);
> ClientConfiguration config = WebClient.getConfig(proxy);
> HTTPConduit conduit1 = (HTTPConduit)config.getConduit();
> conduit1.setReceiveTimeOut(1000);
> This setting gets wiped out (reset to default) after the conduit gets changed
> in the clustering feature e.g. after failover in the FailoveFeature or after
> each request in LoadBalancingFeature.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
