[
https://issues.apache.org/jira/browse/QPID-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-912:
--------------------------------
Attachment: QueueBrowserFailure.txt
I don't have the detail of which QueueBrowser test this was but it shows the
failover caused by the getQueueDepth call when the queue wasn't created. The
concern that should be addressed though is the timeout that occurs shortly
afterwards. It suggests that something isn't being notified correctly when
failover occurs.
> AMQSession.getQueueDepth should better describe its failure conditions.
> -----------------------------------------------------------------------
>
> Key: QPID-912
> URL: https://issues.apache.org/jira/browse/QPID-912
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M2, M2.1
> Reporter: Martin Ritchie
> Attachments: QueueBrowserFailure.txt
>
>
> Summary:
> There are a few things that could do with improvement with the javadoc:
> It suggests that it will retry in the event of failover. It won't... perhaps
> it should.
> It also declares the queue passively as a result if the queue doesn't exist
> then it causes the connection to failover.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
