You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/06/04 11:47:00 UTC
[jira] [Closed] (QPIDJMS-376) notify the ExceptionListener when a
consumer with a MessageListener remotely closes
[ https://issues.apache.org/jira/browse/QPIDJMS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell closed QPIDJMS-376.
----------------------------------
Resolution: Fixed
As I assume you are still using a router with the DISPATCH-962 bug in place, I believe you are probably hitting effectively the same issue I've just identified for someone else on the users list about a related-but-different situation, due to an issue in the failover layers handling of it.
Its worth noting that I wouldn't expect the clients failover handling to be able to handle the situation you describe very pleasantly. I would typically expect it to class the inability to restore the existing consumer as a failed failover attempt and keep trying, but the DISPATCH-962 router bug making it seem like its succeeded in creating the consumer will likely make it act differently currently.
Yes, as this JIRA's changes have been released already, a new JIRA would be needed for further change if made, though commenting on here to establish whats needed first would be fine. Your earlier comment was just missed due to a deluge of updates at the time and being busy with other things.
> notify the ExceptionListener when a consumer with a MessageListener remotely closes
> -----------------------------------------------------------------------------------
>
> Key: QPIDJMS-376
> URL: https://issues.apache.org/jira/browse/QPIDJMS-376
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.31.0
> Environment: AMQP Server: Enmasse 0.17.1
> Enmasse Address Type: anycast
> Reporter: Daniel Maier
> Priority: Major
> Fix For: 0.32.0
>
> Attachments: clientlogs.txt
>
>
> When I create a consumer to an address that just does not exist, I expected to get some exception or that the client retries the operation. But there seems not even to be a log message which indicates a failure.
> Is this intended behavior or is this a bug? A more general description is: If AMQP server closes the receiver link, qpid jms client does not notify the user anyhow or does not re-establish the link.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org