[
https://issues.apache.org/jira/browse/CXF-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815944#comment-13815944
]
Sergey Beryozkin commented on CXF-5378:
---------------------------------------
Hi Roman, interesting case.
CXF Failover feature works if the whole container or the connection goes down,
i.e, if the client even fails to connect.
LoadBalancing feature will always iterate over alternative addresses, but of
course the user may only want to use the alternatives *only if* the preferred
target fails.
I think we may have to consider updating a failover feature to react to
non-found errors too, this is transport-specific so some thinking needs to be
done
Thanks, Sergey
> CXF failover feature doesn't work in osgi
> -----------------------------------------
>
> Key: CXF-5378
> URL: https://issues.apache.org/jira/browse/CXF-5378
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.7.7
> Environment: Karaf 2.3.3 two instances, jax-rs services started on
> Karaf jetty servers
> Reporter: Roman Minko
> Attachments: README.txt, example_cxf_no_locator.zip
>
>
> Failover feature doesn't work in osgi, if jax-rs service was started on Karaf
> jetty server and was stopped as osgi bundle. The bug is reproducible for CXF
> failover feature using pure Karaf 2.3.3 osgi container. After
> NotFoundException consumer doesn't use alternative address.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
