[
https://issues.apache.org/jira/browse/AMQ-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607639#comment-15607639
]
Sergiu Pantiru commented on AMQ-6480:
-------------------------------------
Hi Timothy,
I've tried with 5.14 but this client behaves differently. With 5.7
session.commit() throws and exception when the broker is unavailable. With 5.14
it does not and it waits until the broker is online.
That is even worse for me since i need to release that thread even though the
broker is not available.
Regards,
Sergiu
> receiveNoWait hangs when broker is back up, using failover and prefetch=0
> -------------------------------------------------------------------------
>
> Key: AMQ-6480
> URL: https://issues.apache.org/jira/browse/AMQ-6480
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Reporter: Sergiu Pantiru
>
> I have a consumer that keeps a message(session opened) for 1 minute and than
> acknowledges it and commits the session. The thread is finished once the
> session is closed.
> If ActiveMq dies before message is ack, i still close the session/consumer to
> free the thread.
> When ActiveMq is back up, a new thread (new consumer/session) tries to
> receiveNoWait and this call blocks because it does not receive any message.
> There is a poison ack sent before it hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
