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 twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: "Bart van Leeuwen" <bart_van_leeu...@netage.nl> To: users@activemq.apache.org Date: 26-04-2022 20:20 Subject: Re: ActiveMQ 5.15 vs 5.16 behaviour on durable topics 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 tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: "Jonathan Gallimore" <jonathan.gallim...@gmail.com> To: users@activemq.apache.org Date: 26-04-2022 18:18 Subject: Re: ActiveMQ 5.15 vs 5.16 behaviour on durable topics 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 (where the transactions would be managed by TomEE) so it looks like the messages are being rolled back and delivery re-attempted. Setting the connection factory's TransactionSupport to none in TomEE seems to do the trick. Hope that helps, but please let us know if you have any queries. Thanks Jon On Tue, Apr 26, 2022 at 4:39 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > 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 reproducer - I confirm I can see the same issue, and also > see it with TomEE 8.0.11. I'll report back here with anything I find. > > Jon > > On Sun, Apr 24, 2022 at 10:22 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Hi Bart, >> >> Thanks a lot. I should have time later today or tomorrow to investigate. >> >> I'm working on ActiveMQ 5.17.1 right now (it should be up for a vote >> later today). >> >> Regards >> JB >> >> On Sun, Apr 24, 2022 at 10:12 AM Bart van Leeuwen >> <bart_van_leeu...@netage.nl> wrote: >> > >> > Hi JB, >> > >> > I've assembled a testcase which you can find here: >> > https://github.com/semanticfire/amqdurtopic >> > Let me know if things are unclear. >> > >> > Met Vriendelijke Groet / With Kind Regards >> > Bart van Leeuwen >> > >> > >> > twitter: @semanticfire >> > tel. +31(0)6-53182997 >> > Netage B.V. >> > http://netage.nl >> > Esdoornstraat 3 >> > 3461ER Linschoten >> > The Netherlands >> > >> > >> > >> > >> > From: "Jean-Baptiste Onofré" <j...@nanthrax.net> >> > To: users@activemq.apache.org >> > Date: 24-04-2022 07:29 >> > Subject: Re: ActiveMQ 5.15 vs 5.16 behaviour on durable topics >> > ________________________________ >> > >> > >> > >> > Hi Bart, >> > >> > do you have a simple test case to reproduce the behavior change ? >> > >> > Regards >> > JB >> > >> > On Sat, Apr 23, 2022 at 11:58 AM Bart van Leeuwen < >> > bart_van_leeu...@netage.nl> wrote: >> > >> > > Hi, >> > > >> > > I´ve been using ActiveMQ as part of Tomee Plus for a long time with >> great >> > > satisfaction. >> > > >> > > I use a durable topic to communicate information to a webapp through a >> > > long pol in a servlet. This suits my needs and has worked without >> issues so >> > > far. >> > > With a recent tomee upgrade I moved from AMQ 5.15.x to 5.16.x and see >> a >> > > total new behaviour. >> > > >> > > My clients will receive the message on the topic multiple times ( >> > > practically maximumRedeliveries + 1) so if maximumRedeliveries = 2 >> then the >> > > client will receive the message 3 times. >> > > The Dispatch counter in the console will show maximumRedeliveries + 2 >> for >> > > every message. >> > > >> > > There is nothing in the logs, and the java servlet reading the topic >> is a >> > > plain and simple durable topic subscriber as can be found in the >> numerous >> > > examples on the web. >> > > >> > > I´ve tried going over the changelog and documentation but I cannot >> find a >> > > issue or setting that seems related to what I observe. >> > > >> > > Any help greatly appreciated! >> > > >> > > Met Vriendelijke Groet / With Kind Regards >> > > Bart van Leeuwen >> > > >> > > >> > > twitter: @semanticfire >> > > tel. +31(0)6-53182997 >> > > Netage B.V. >> > > http://netage.nl >> > > Esdoornstraat 3 >> > > 3461ER Linschoten >> > > The Netherlands >> > > >> > >> > >> >
