activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1818) Reconnecting core JMS client won't re-create auto-created queue
Date Thu, 19 Apr 2018 19:45:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444688#comment-16444688
] 

ASF GitHub Bot commented on ARTEMIS-1818:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2034

    ARTEMIS-1818 re-create auto-created queue on JMS reconnect

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1818

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2034.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2034
    
----
commit 94fc317081f3ac3a6f87d21e8f076be08e660aa7
Author: Justin Bertram <jbertram@...>
Date:   2018-04-19T19:42:39Z

    ARTEMIS-1818 re-create auto-created queue on JMS reconnect

----


> Reconnecting core JMS client won't re-create auto-created queue
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-1818
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1818
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> Scenario:
> * Start broker
> * core JMS client sends message to queue
> * broker auto-creates queue & receives message
> * core JMS client creates consumer on queue and consumes the message; consumer's connection
uses reconnectAttempts=-1
> * stop broker
> * during shutdown the consumer is disconnected and since the message-count is already
0 that means the broker will auto-delete the consumer's queue
> * start broker
> * consumer automatically reconnects
> * broker throws an error that the consumer's queue doesn't exist
> * consumer is broken and will not receive any messages



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message