I have an existing RedeliveryPolicy configured thusly:
This has been working fine up through 5.5.1. Today I upgraded to 5.7.0 and
now my application won't start:
y'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with nam
:
chudak wrote
>
> Did you ever solve this problem?
>
> I've been using atomikos, spring DMLC and activemq for several years.
> Recently I started using camel and we are having this exact same problem.
> With the camel endpoints polling (which effectively doubled the numbe
Did you ever solve this problem?
I've been using atomikos, spring DMLC and activemq for several years.
Recently I started using camel and we are having this exact same problem.
With the camel endpoints polling (which effectively doubled the number of
message listener containers I previously had) e
I figured this out but it was in no way obvious...
I had to add this to the DMLC:
Hope this helps someone else avoid wasting a whole day..
Charles
chudak wrote:
>
> I'm having a problem with message redelivery.
>
> I'm using:
>
> ActiveMQ 5.3.0
> Spring
I'm having a problem with message redelivery.
I'm using:
ActiveMQ 5.3.0
Spring 2.5.6
Spring Integration 1.0
Atomikos 3.5.9
If I send a 'broken' message to my queue, the transaction rolls back
correctly but it NEVER gets redelivered even if I restart both the client
(application) and the broker.
