[
https://issues.apache.org/jira/browse/ARTEMIS-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066095#comment-16066095
]
ASF GitHub Bot commented on ARTEMIS-1246:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1365
@clebertsuconic
> you would eventually see this issue when using older clients:
>
> AMQ119019: Queue already exists
I hope it doesn't happen anymore after this fix!
To reproduce it and to have proper tests on it I see 2 solutions:
1. having unit tests on protocol handling that emulate old clients message
flow
2. having a new "compatibility-tests" folder with tests that verify JMS
behaviours with different old clients
But neither seems a simple and effetive solution to be done now; did you
see other ways to test it?
> AMQ119019: Queue already exists
> -------------------------------
>
> Key: ARTEMIS-1246
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1246
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Blocker
>
> Using old versions (<1.5.4) of the JMS Client (with CORE protocol), JMS temp
> queues will rise javax.jms.InvalidDestinationException: AMQ119019: Queue
> already exists.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
