qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "linuxta (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DISPATCH-175) Router continues to forward messages to the broker even when the broker is not available
Date Tue, 29 Sep 2015 21:57:06 GMT
linuxta created DISPATCH-175:
--------------------------------

             Summary: 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


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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message