[
https://issues.apache.org/jira/browse/ARTEMIS-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502986#comment-16502986
]
Lionel Cons commented on ARTEMIS-1900:
--------------------------------------
Good news: I've managed to create a small script to reproduce the problem. ItÂ
simply starts two threads that both create a (different) subscription on the
same queue. See the attached {{ARTEMIS-1900.pl}}. All the used Perl modules are
available in CPAN but the code is so simple that you may want to build a Java
test out of it.
It does not always trigger the problem but when it does, its output shows the
few STOMP frames that have been exchanged:
{code}
$ ./ARTEMIS-1900.pl
# 2018/06/06-10:18:16 1900[24710.1]: encoding CONNECT frame
# 2018/06/06-10:18:16 1900[24710.1]: H passcode:manager
# 2018/06/06-10:18:16 1900[24710.1]: H accept-version:1.0,1.1,1.2
# 2018/06/06-10:18:16 1900[24710.1]: H host:xxx
# 2018/06/06-10:18:16 1900[24710.1]: H login:system
# 2018/06/06-10:18:16 1900[24710.2]: encoding CONNECT frame
# 2018/06/06-10:18:16 1900[24710.2]: H passcode:manager
# 2018/06/06-10:18:16 1900[24710.2]: H accept-version:1.0,1.1,1.2
# 2018/06/06-10:18:16 1900[24710.2]: H host:xxx
# 2018/06/06-10:18:16 1900[24710.2]: H login:system
# 2018/06/06-10:18:17 1900[24710.1]: decoding CONNECTED frame
# 2018/06/06-10:18:17 1900[24710.1]: H version:1.2
# 2018/06/06-10:18:17 1900[24710.1]: H session:32c8e23c
# 2018/06/06-10:18:17 1900[24710.1]: H server:ActiveMQ-Artemis/2.7.0-SNAPSHOT
ActiveMQ Artemis Messaging Engine
# 2018/06/06-10:18:17 1900[24710.1]: encoding SUBSCRIBE frame
# 2018/06/06-10:18:17 1900[24710.1]: H destination:/queue/test.1900
# 2018/06/06-10:18:17 1900[24710.1]: H id:f8d858-5b1798c8-6086-d309-1
# 2018/06/06-10:18:17 1900[24710.1]: H receipt:f8d858-5b1798c8-6086-d309-2
# 2018/06/06-10:18:17 1900[24710.2]: decoding CONNECTED frame
# 2018/06/06-10:18:17 1900[24710.2]: H version:1.2
# 2018/06/06-10:18:17 1900[24710.2]: H session:b6a36406
# 2018/06/06-10:18:17 1900[24710.2]: H server:ActiveMQ-Artemis/2.7.0-SNAPSHOT
ActiveMQ Artemis Messaging Engine
# 2018/06/06-10:18:17 1900[24710.2]: encoding SUBSCRIBE frame
# 2018/06/06-10:18:17 1900[24710.2]: H destination:/queue/test.1900
# 2018/06/06-10:18:17 1900[24710.2]: H id:12bc748-5b1798c8-6086-7caa-1
# 2018/06/06-10:18:17 1900[24710.2]: H receipt:12bc748-5b1798c8-6086-7caa-2
# 2018/06/06-10:18:17 1900[24710.2]: decoding ERROR frame
# 2018/06/06-10:18:17 1900[24710.2]: H message:AMQ339016 Error creating
subscription 12bc748-5b1798c8-6086-7caa-1
# 2018/06/06-10:18:17 1900[24710.2]: H content-type:text/plain
# 2018/06/06-10:18:17 1900[24710.2]: H content-length:41
# 2018/06/06-10:18:17 1900[24710.1]: decoding RECEIPT frame
# 2018/06/06-10:18:17 1900[24710.1]: H receipt-id:f8d858-5b1798c8-6086-d309-2
# 2018/06/06-10:18:17 1900[24710.1]: H receipt-id:f8d858-5b1798c8-6086-d309-2
# 2018/06/06-10:18:17 1900[24710.2]: encoding DISCONNECT frame
Thread 2 terminated abnormally: unexpected ERROR frame received: AMQ339016
Error creating subscription 12bc748-5b1798c8-6086-7caa-1
# 2018/06/06-10:18:20 1900[24710.1]: encoding DISCONNECT frame
# 2018/06/06-10:18:20 1900[24710.1]: H receipt:f8d858-5b1798c8-6086-d309-3
# 2018/06/06-10:18:20 1900[24710.1]: decoding RECEIPT frame
# 2018/06/06-10:18:20 1900[24710.1]: H receipt-id:f8d858-5b1798c8-6086-d309-3
{code}
As expected, the broker logs:
{code}
2018-06-06 10:18:17,858 WARN [org.apache.activemq.artemis.core.protocol.stomp]
AMQ222069: Sent ERROR frame to STOMP client /x.x.x.x:x: AMQ339016 Error
creating subscription 12bc748-5b1798c8-6086-7caa-1
{code}
And I've tried with {{<auto-delete-queues>false</auto-delete-queues>}}: it
makes no difference.
> 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)
