You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Yaytay (JIRA)" <ji...@apache.org> on 2011/03/28 10:08:05 UTC
[jira] [Updated] (CXF-3424) LoadDistributorFeature for CXF
[ https://issues.apache.org/jira/browse/CXF-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yaytay updated CXF-3424:
------------------------
Attachment: LoadDistributor1.diff
Patch attached.
A full build fails tests in jax-rs, but they seem to be failing anyway, without my code.
This version does not attempt to establish an Exchange-independent list of endpoints to distribute between (whereas it does attempt to establish an Exchange-independent list of addresses).
It would be possible to modify AbstractStaticFailoverStrategy to cache the endpoint list and return that if a null Exchange is passed to getAlternateEndpoints, but I'm not sure about the validity of doing so and I'm only going to use it with multiple addresses :)
Any comments gratefully received.
> LoadDistributorFeature for CXF
> ------------------------------
>
> Key: CXF-3424
> URL: https://issues.apache.org/jira/browse/CXF-3424
> Project: CXF
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.3.3
> Reporter: Yaytay
> Priority: Minor
> Attachments: LoadDistributor1.diff
>
>
> The FailoverTargetSelector in CXF takes effect only when a transport failure occurs, so it provides no way to spread the load across a number of addresses or endpoints.
> By subclassing the FailoverTargetSelector and the FailoverFeature it is possible to provide a load distributor that works for most circumstances.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira