[
https://issues.apache.org/jira/browse/CXF-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826385#comment-13826385
]
Sergey Beryozkin commented on CXF-5382:
---------------------------------------
Hi Jacek, I think the only way to support the sharing of various HTTP conduit
properties is to introduce a Spring or Blueprint HTTP conduit which would have
a wide enough URL pattern which would match all the alternative HTTP addresses.
Can you give it a try please ?
Cheers
> 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
>
> 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)
