[
https://issues.apache.org/jira/browse/ARTEMIS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142348#comment-17142348
]
Justin Bertram commented on ARTEMIS-2817:
-----------------------------------------
Can you attach your {{broker.xml}}?
Also, can you [enable STOMP frame logging as described in the
documentation|http://activemq.apache.org/components/artemis/documentation/latest/stomp.html#logging]
then reproduce the error and attach the log?
In order to investigate (and potentially fix) the issue I need a way to
reproduce it.
> Stomp.py creates a misleading error and fails to listen on queue
> ----------------------------------------------------------------
>
> Key: ARTEMIS-2817
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2817
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Affects Versions: 2.13.0
> Reporter: BENJAMIN Lee WARRICK
> Assignee: Justin Bertram
> Priority: Major
>
> I've been using stompy.py (version 5.0.1) to publish and subscribe on Artemis
> 2.8.1. However now that installed a new instance, this time Artemis 2.13.0.,
> the client fails to subscribe. I can successfully publish to the address with
> STOMP, but when I try to subscribe to a queue, I get the following error:
> "received an error "AMQ229019: Queue [queue name] already exists on address
> [address name]"
> And no messages are pulled. I also tried upgrading to stomp.py 6.0, but I
> still get the same error. Using a Java JMS client I am able to subscribe.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)