Well, jms.redeliveryPolicy.nonBlockingRedelivery=true gave a big ol' error about not being recognized. I haven't confirmed that it's not blocking yet, but jms.nonBlockingRedelivery=true is at least accepted without error. (*Chris*)
On Tue, Jul 31, 2012 at 1:10 PM, Timothy Bish <tabish...@gmail.com> wrote: > On Tue, 2012-07-31 at 13:04 -0700, Chris Pratt wrote: > > Is the URL parameter nonBlockingRedelivery=true, > > jms.nonBlockingRedelivery=true, > > jms.redeliveryPolicy.nonBlockingRedelivery=true, or something else > entirely? > > (*Chris*) > > > > On Tue, Jul 31, 2012 at 2:57 AM, Gary Tully <gary.tu...@gmail.com> > wrote: > > > > I believe its: jms.redeliveryPolicy.nonBlockingRedelivery=true > > > > The broker variant will be in 5.7, so you can try a 5.7-SNAPSHOT > > > see: https://issues.apache.org/jira/browse/AMQ-3894 > > > > > > The implementation in 5.6 is configured on a connection factory as it > > > augments the existing redelivery policy: > > > https://issues.apache.org/jira/browse/AMQ-1853 > > > > > > On 30 July 2012 21:02, Chris Pratt <thechrispr...@gmail.com> wrote: > > > > Is it possible to configure the new ActiveMQ 5.6 Non-Blocking > Redelivery > > > in > > > > the Broker itself? Or can it only be done in the ConnectionFactory > on > > > the > > > > client? If it is possible, does anyone have a short example of a > proper > > > > activemq.xml that might show me how to achieve this? Thanks. > > > > (*Chris*) > > > > > > > > > > > > -- > > > http://fusesource.com > > > http://blog.garytully.com > > > > > -- > Tim Bish > Sr Software Engineer | FuseSource Corp > tim.b...@fusesource.com | www.fusesource.com > skype: tabish121 | twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
