Closed georgesberscheid closed 1 year ago
Update: it works if I set autoCreateAddresses and autoCreateQueues to true in the broker configuration. According to the documentation this is used to automatically create addresses and queues when a client connects, which is what I wanted to prevent from happening. I only want addresses and queues that have explicitly been defined using ActiveMQArtemisAddress.
Are you able to reproduce this issue using the latest version of the operator?
This issue has been closed because it has not been updated in the last 6 months. Feel free to reopen it if it is still valid.
Describe the bug I got the operator running and a cluster of 3 brokers that look fine. I also enabled the console and can access it through an ingress. I'm now trying to deploy a queue using a ActiveMQArtemisAddress resource, but nothing appears in the broker logs and the queue doesn't show up in the console.
Bonus question: how do I join the Slack chatroom https://artemiscloudio.slack.com? Looks like I need an invitation ;-)
Here is the definition of the broker:
To Reproduce Create testqueue.yaml:
Deploy the file:
Nothing happens. I also tried restarting the broker instances but that didn't help either.
The resource is properly created though:
Looking at the logs from the operator, it seems that it tries to create something though:
Platform (please complete the following information):
Expected behavior The address & queue are created and visible in the console and can be used by the application.
Actual behavior Nothing happens. The address and queue are not created and cannot be used by an application.
Addtional context I have a JBoss EAP instance pointed to the Artemis instance which throws the following exception: