[
https://issues.apache.org/jira/browse/AMQ-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418264#comment-13418264
]
Timothy Bish commented on AMQ-3932:
-----------------------------------
It seems valid that in the case where the transport is not connected the
receiveNoWait and the timed receive as well should just return null to indicate
that there's not currently a message available since in the timed case you
could end up waiting much longer than the intended time otherwise.
> receiveNoWait hangs when broker is down, using failover and prefetch=0
> ----------------------------------------------------------------------
>
> Key: AMQ-3932
> URL: https://issues.apache.org/jira/browse/AMQ-3932
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.6.0
> Reporter: Andrew McDonnell
> Assignee: Timothy Bish
> Attachments: AMQ3932Test.java
>
>
> I have a connection set up using failover and queuePrefetch=0. I create a
> consumer, stop the broker, and call receiveNoWait.
> I would expect this to return/throw immediately; instead it hangs. Without
> failover or with a non-zero prefetch it works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
