[
https://issues.apache.org/jira/browse/ARTEMIS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872412#comment-16872412
]
Justin Bertram commented on ARTEMIS-2398:
-----------------------------------------
I'm not familiar with this "gateway" you're talking about so I can't answer
your questions about it. This is not a concept native to an ActiveMQ Artemis
cluster.
Also, I'm not quite sure why you're talking about slaves in this context. In
ActiveMQ Artemis a "slave" refers to the inactive backup node in a master/slave
pair. Since these nodes are inactive they do not actively participate in the
cluster until their corresponding master dies. You seem to be referring to
normal nodes as "slave" nodes. Can you shed any light on this?
> 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)
