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 wrote:
> On Tue
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 wrote:
>
I belie
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 wrote:
> The broker variant will be in 5.7, so you can try a 5.7-SNAPSHOT
> see: htt
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,
