Thanks for following up. I sent a PR which has been merged. This will be
fixed in the next release.
Thanks for the bug report!
Justin
On Tue, Jul 29, 2025 at 1:21 PM Philip
wrote:
> There seems to be no stacktrace as it probably gets caught somewhere and
> not rethrown.
> There is only this w
There seems to be no stacktrace as it probably gets caught somewhere and not
rethrown.
There is only this warning which is why this problem initially was so
perplexing. I just overlooked it because it was hidden between other debug logs.
2025-07-29 20:13:53,341 WARN
[org.springframework.jms.Jm
Do you happen to have the stack-trace from the NPE? I'd like to add it to
the Jira for posterity's sake.
Justin
On Tue, Jul 29, 2025 at 11:02 AM Philip
wrote:
>
> You are indeed correct that I am using an old broker (Wildfly 10).
>
> I am unable to provide a complete demo project as this would
WildFly 10 was released almost 10 years ago and it contains ActiveMQ
Artemis 1.1.0. This is why it's not sending back the "configurationManaged"
flag.
I opened ARTEMIS-5596 [1] to deal with this. In the meantime your options
are:
1. Downgrade your client to 2.17.0.
2. Upgrade the broker to 2.
You are indeed correct that I am using an old broker (Wildfly 10).
I am unable to provide a complete demo project as this would be more complex
than it is worth.
I have created a GitHub repository in which the general JMS setup is
duplicated with a description of the rest of the setup and the
Do you have a sample project or anything that we can use to reproduce what
you're seeing? At this point, the only way I can see how you might be
getting null there is if you were using a newer client with an older
broker, but it's certainly possible I'm not seeing all the possibilities.
Regardless,
I should have been more clear about my exact setup.
I am trying to create multiple consumers that either listen to a JMS queue or a
JMS topic.
Each consumer listening to a queue has no client ID as it is not needed.
Each consumer listening to a topic has both a client ID (the same one for all
co
The simplest way to investigate is with code that reproduces the problem.
Do you have a sample project or anything that we can use to reproduce what
you're seeing?
Also, what version of ActiveMQ Artemis are you using on the broker and the
client?
Lastly, can you clarify your use-case? It seems yo
