[
https://issues.apache.org/jira/browse/ARTEMIS-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873010#comment-16873010
]
Martijn commented on ARTEMIS-2398:
----------------------------------
I haven't worked with a artemis cluster before so forgive the incorrect use of
thermologie.
When connecting to a artemis cluster you need to supply a group address and
group port. I'm guessing that the machine that is running on that address and
the software running on that port acts as a sort of loadbalancer for all the
nodes? It receives a request and then determines which node actiually receives
the message/object? If that is correct, can we get a list of nodes from the
group "loadbalancer"? If not is there any way at all to get a list of nodes
that belong to the cluster?
> 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)
