[jira] [Commented] (ARTEMIS-1900) Unexpected STOMP subscription errors (AMQ339016+AMQ119017)

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram commented on ARTEMIS-1900:
-----------------------------------------

Can you elaborate any further on the actual use-case from your stress test?  Clearly you have a client attempting to create a subscription, but I assume that's not all the test is doing.  Without more details there's not much guidance to conduct an investigation.

> 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
>
> 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)