All, Just to update, I was able to solve the problem, by changing how I declare the transactionManager. The problem was that it wasn't committing the transaction automatically, as apparently it was previously with 4.1.1. I'm still not 100% I have things configured correctly, but it seems good so far...
I ended up adding the transactionManager to the DefaultMessageListenerContainer spring config (previously it was being set on the PooledConnectionPool object). Jason Jason Rosenberg wrote: > > Hi, > > I wonder if there's a quick/obvious explanation to help me past this one > (if not, I'll post more details of my particular use case)..... > > Basically, after upgrading to 5.0.0 from 4.1.1, everything seems to be > working fine, except, each time I restart my client (without restarting > the broker), the client gets redelivered all the same messages that it > received prior to the restart..... > > I suspect there's some sort of change to the default message > acknowledgement config? > > I am using queues only, and I'm using Spring's > DefaultMessageListenerContainer for receiving message. The default for > this should be auto-acknowledge, and I haven't changed anything with it, > it should just use the defaults... > > I'm wondering if it could have to do with the optimizeAcknowledge setting, > I haven't ever set that, could it be related? > > I'm also setting redelivery policies on the queues, not sure if that might > be related as well.... > > Jason > -- View this message in context: http://www.nabble.com/Problem-with-message-redelivery%2C-after-upgrade-from-4.1.1-to-5.0.0-tp15051335s2354p15056283.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
