[
https://issues.apache.org/jira/browse/ARTEMIS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871165#comment-16871165
]
Justin Bertram commented on ARTEMIS-2398:
-----------------------------------------
I've got a couple of questions:
* What client protocol are you using? Most clients support queue auto-creation
which should handle the vast majority of use-cases.
* If you connect to the same node which received the "createQueue" command does
the client find the queue?
For what it's worth, management operations like "createQueue" aren't designed
to be propagated across a cluster. Each node can have it's own set of queues.
Changing this behavior would be a feature request.
> In cluster mode, Artemis ignores createQueue command
> ----------------------------------------------------
>
> Key: ARTEMIS-2398
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2398
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martijn
> Priority: Major
>
> We are using standalong artemis on our servers and this works great. We have
> created an autoconfigurer who automatically creates queues on startup. We can
> see that the queues are created.
> We are switching to a artemis cluster. We have updated our code and we can
> verify that our application is connecting to the new artemis cluster however
> the queues aren't created. It seams as if the createqueue command isn't
> passed on to the artemis nodes.
> To create the queues we use the following code:
> {code:java}
> // ManagementHelper.putOperationInvocation(message,
> "broker",
> "createQueue",
> queueName,
> queueName,
> null,
> true,
> "ANYCAST");
> {code}
> This works for standalone however not for a artemis cluster.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
