[
https://issues.apache.org/jira/browse/ARTEMIS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872089#comment-16872089
]
Martijn commented on ARTEMIS-2398:
----------------------------------
Thanks for your comment and questions. Your questions have made me think about
a few things. The cluster has 1 single point of entry (A kind of gateway). When
it receives a command, like createQueue for example, does it select a
slave/node and then send the command to that node? By doing so ignoring the
other slaves?
Is it possible to ask the "gateway" for a list of slaves so that we can then
manually tell all the slaves to create queues? So that all the slaves that the
queue created?
> 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)
