[
https://issues.apache.org/jira/browse/ARTEMIS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504808#comment-16504808
]
ASF subversion and git services commented on ARTEMIS-1900:
----------------------------------------------------------
Commit 7b49a8e3d2f38fc97311b46d7ebd395e5b88b879 in activemq-artemis's branch
refs/heads/2.6.x from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=7b49a8e ]
ARTEMIS-1900 fix race in STOMP auto-create
(cherry picked from commit dc29a55e1b0106ddaf8e332d098cde4520bd639e)
> 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)
