I believe I see why this is working for you in ActiveMQ "Classic."
By default ActiveMQ "Classic" will block any messages published to an MQTT
topic starting with '$' [1]. However, a configuration element named
"publishDollarTopics"
was added [2] a long time ago to assist "legacy MQTT
Hi
I'm glad that works, and thanks for letting us know. The change in question
I believe is this one:
https://github.com/apache/tomee/commit/accb2418a736916d724a3abd491bde998516021f
- and this is the associated JIRA:
https://issues.apache.org/jira/browse/TOMEE-2941.
The change itself was in
Hi Jon,
I've applied the transaction setting to tomee.xml of the test server of
the full application and indeed the problem is gone now.
Question remains, what has changed since 8.0.4 that causes this default
behavior change
Met Vriendelijke Groet / With Kind Regards
Bart van Leeuwen
JB submitted 5.17.1 to a vote yesterday which includes this change:
https://lists.apache.org/thread/strs8odwmtps91bfo65jjwt65y0jockq.
Assuming all goes well that should be released very soon. Can you upgrade to
that?
- Lucas
On 2022-04-26, 9:30 AM, "Peter Raymond" wrote:
CAUTION:
Hi Jon,
Thanks for looking into this, i've merged your changes, but I still have
the same behaviour in the testcase.
Did something change between Tomee 8.0.4 and 8.0.5 that the XA
transactions are default?
Met Vriendelijke Groet / With Kind Regards
Bart van Leeuwen
twitter: @semanticfire
Hi,
Is there a roadmap for ActiveMQ releases? I am wondering when ActiveMQ Broker
5.16.5 will be released?
We are waiting on the 5.16.5 release because it looks like it will include a
fix for this issue:
https://issues.apache.org/jira/browse/AMQ-8556
Which resolves
I sent you a PR for your example project:
https://github.com/semanticfire/amqdurtopic/pull/1
The connection factory you're using is set to use XA transactions (which is
the default in TomEE) and this will create connections that expect to be
used in a transactional way. You're not using MDBs
Hi, Apache TomEE contributor here :)
Just a heads-up that I'm looking at this on the TomEE side as well. I
recall that there were a couple of changes on the TomEE side around the
time we picked up ActiveMQ 5.16.x, so its worth us checking that there
isn't an issue there.
Thanks for your
> It’s a huge problem for us since in Kapua we are doing # subscriptions
(for internal components) and using $ as topic prefix (also Kura is using
this in its namespace) and worked perfectly with ActiveMQ 5.x.
This use-case is clearly prohibited by the MQTT specification. It
specifically says:
I assumed that since you could only reproduce the NPE with your plugins
added you were able to identify the root cause of the problem. I gave up
trying to reproduce the problem in Kapua due to a lack of clarity around
running the actual test. I'll go back and take another look at reproducing
it,
Ah yes this is via a lb on different ports. Thanks for the pointer.
On Tue, Apr 26, 2022, 11:30 AM Dondorp, Erwin
wrote:
> Dave,
>
> > One thing that could help a bit would be to bookmark a set of tabs in
> the browser but unfortunately when logging into a broker any existing
> session for
Dave,
> One thing that could help a bit would be to bookmark a set of tabs in the
> browser but unfortunately when logging into a broker any existing session for
> another broker is invalidated.
> Perhaps there is a broker-side setting in hawtio to allow multiple concurrent
> sessions for
One thing that could help a bit would be to bookmark a set of tabs in the
browser but unfortunately when logging into a broker any existing session
for another broker is invalidated. Perhaps there is a broker-side setting
in hawtio to allow multiple concurrent sessions for different brokers in
one
Sorry but I cannot test the fix due to the NPE.
And even the “normal” stealing link doesn’t work (same NPE) with our plugin
code.
I don’t know which is the best way to investigate further.
So, unfortunately, I cannot say if this fix fits or not our needs since I
cannot test it.
Riccardo
Da:
It’s a huge problem for us since in Kapua we are doing # subscriptions (for
internal components) and using $ as topic prefix (also Kura is using this in
its namespace) and worked perfectly with ActiveMQ 5.x.
I should evaluate the impact but I’m not so sure we can move to Artemis with
this
15 matches
Mail list logo
