You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/06/07 15:32:00 UTC
[jira] [Updated] (ARTEMIS-1900) Race condition in STOMP auto-create
causing errors (AMQ339016+AMQ119017)
[ https://issues.apache.org/jira/browse/ARTEMIS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-1900:
------------------------------------
Summary: Race condition in STOMP auto-create causing errors (AMQ339016+AMQ119017) (was: Unexpected STOMP subscription errors (AMQ339016+AMQ119017))
> Race condition in STOMP auto-create causing errors (AMQ339016+AMQ119017)
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-1900
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1900
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Reporter: Lionel Cons
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.7.0, 2.6.2
>
> 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)