[
https://issues.apache.org/jira/browse/DISPATCH-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved DISPATCH-82.
---------------------------------
Resolution: Fixed
> Poor error handling by qdmanage and qdstat tools.
> -------------------------------------------------
>
> Key: DISPATCH-82
> URL: https://issues.apache.org/jira/browse/DISPATCH-82
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.2
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.3
>
>
> The command line tools qdmanage and qdstat behave poorly if there is a
> problem connecting to the router. For exaample if no router is running at all
> you see this output
> recv: Connection refused
> [0x1ce68f0]:ERROR amqp:connection:framing-error SASL header mismatch:
> Insufficient data to determine protocol [''] (connection aborted)
> CONNECTION ERROR connection aborted (remote)
> send: Broken pipe
> Then the tool hangs for almost 2 seconds, then we see:
> ValueError: Failed to subscribe to amqp://0.0.0.0:amqp/#
> The tool should immediately print a simple "Connection to ... refused".
> In the case of an invalid hostname we get this message:
> /usr/local/bin/qdstat: MessengerException - Cannot subscribe to
> amqp://foobar:amqp/#
> We should see something like "Unknown host foobar"
> If the router crashes during a request it takes 10 seconds for the client to
> time out. Detecting a TCP disconnect should happen much more quickly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
