OK.. I think this is a bug.. looks like rollback just adds it back to unconsumedMessages if nonBlockingRedelivery = false but forgets to call the messageActivityListener telling us that there's a message available to be read.
Seems to be clearly a bug.. but I think I have a work around to turn on nonBlockingRedelivery... On Thu, Jun 9, 2016 at 6:22 PM, Kevin Burton <bur...@spinn3r.com> wrote: > I'm trying to use a message available listener to notify me when I have a > message after a rollback. > > https://gist.github.com/burtonator/ebf06a7238bd9a1273853ce5282acf02 > > I'm doing this so that I can do non-blocking receive. > > However, it's only called once, in the initial receive. Even if I do 5 > rollbacks I only get the event on the first message the first time its > delivered. > > Any thoughts as to what I'm doing wrong here? > > Stumped on this one.. at last I tracked it down though. Wasted half a day > already. > > -- > > We’re hiring if you know of any awesome Java Devops or Linux Operations > Engineers! > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > > -- We’re hiring if you know of any awesome Java Devops or Linux Operations Engineers! Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts>
