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

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

GitHub user jbertram opened a pull request:

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

    ARTEMIS-1900 fix race in STOMP auto-create

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/2127.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 #2127
    
----
commit 19ece620053b550cda43e4ede230009a999d668a
Author: Justin Bertram <jbertram@...>
Date:   2018-06-04T19:27:31Z

    ARTEMIS-1900 fix race in STOMP auto-create

----


> Unexpected STOMP subscription errors (AMQ339016+AMQ119017)
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-1900
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1900
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Lionel Cons
>            Priority: Major
>         Attachments: ARTEMIS-1900.pl
>
>
> When stress testing Artemis (latest snapshot) using STOMP, I sometimes see 
> subscription creation errors (AMQ339016). This is not reproducible so this is 
> probably a concurrency issue.
> The STOMP client receives an {{ERROR}} frame that contains in its {{message}} 
> header:
> {code}
> AMQ339016 Error creating subscription xyz
> {code}
> and in its body:
> {code}
> AMQ119017: Queue abc does not exist.
> {code}
> Also, this error is only sent to the client and not logged by the broker. 
> IMHO, every time the broker reports a fatal client error (i.e. STOMP 
> {{ERROR}} frame) it should also log this as a warning on its side. Let me 
> know if this is specific to this case or if I should log a separate Jira 
> issue to track this.



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

Reply via email to