[
https://issues.apache.org/jira/browse/DISPATCH-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-175.
-------------------------------
Resolution: Fixed
Assignee: Ted Ross
Fix Version/s: 0.6.0
> Router continues to forward messages to the broker even when the broker is
> not available
> ----------------------------------------------------------------------------------------
>
> Key: DISPATCH-175
> URL: https://issues.apache.org/jira/browse/DISPATCH-175
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 0.5
> Environment: Red Hat
> Reporter: linuxta
> Assignee: Ted Ross
> Fix For: 0.6.0
>
>
> Config router to connect to a single broker.
> When the broker is down, the router continues to forward messages received
> from clients to the broker. This causes message loss.
> Log looks like this:
> SERVER (trace) Connection to (broker ip) failed
> SERVER (trace) Connecting to (broker ip)
> SERVER (trace) Connecting to (broker ip)
> ...
> MESSAGE (trace) Receiving Message ...
> MESSAGE (trace) Sending Message ...
> SERVER (trace) Connecting to (broker ip)
> Should proton clients get some kind of error?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
