activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-1900) Unexpected STOMP subscription errors (AMQ339016+AMQ119017)
Date Thu, 07 Jun 2018 15:32:00 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Bertram updated ARTEMIS-1900:
------------------------------------
    Component/s: STOMP

> Unexpected STOMP subscription 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)

Mime
View raw message