Thanks for your detailed answer Claus.
But that's what I mean with "may it works as a work around". Because for
each different ActiveMQComponent we create a new ActiveMQConnectionFactory.
Does this sound right for you? Should we do not support a more elegant and
resource friendly solution? Somethin
On Sun, Jul 31, 2011 at 7:42 PM, Christian Müller
wrote:
> Hello Claus!
>
> As you know, the redelivery logic is part of Apache ActiveMQ, but we cannot
> use it in Camel in the way I would like it. To only have one redelivery
> policy in place is not sufficient for us (if you configure the redeliv
For clarification:
We have multiple services/bundles running inside one ServiceMix instance and
sharing the same ActiveMQConnectionFactory which is exported as OSGI service
by the activemq-broker.xml configuration.
We could use a separate ActiveMQConnectionFactory for each service/bundle,
but this
Hello Claus!
As you know, the redelivery logic is part of Apache ActiveMQ, but we cannot
use it in Camel in the way I would like it. To only have one redelivery
policy in place is not sufficient for us (if you configure the redelivery
policy in your ActiveMQConnectionFactory). We have multiple app
Frankly I thing the redelivery logic should be part of Apache ActiveMQ.
Your solution is brittle in the fact that you consume the message, and
then send it back to the broker. What happens if you cannot send the
message back to the broker?
It would be better if the broker handled all this out of t
Hello guys and thank you for your answers/opinions!
Sorry for my late reply, but I was busy with some other tasks. But I didn't
forgot you... ;-)
@Ben: Looks like we share the same thoughts. I think your suggestion is
really simple (I like simple solutions) and works for most of our
requirements.
Hi Christian,
Why don't you simply define the redelivery policy on the
TransactionErrorHandler like that :
http://camel.apache.org/schema/spring";>
Hi Christian,
You don't need to configure the activemq component with the name of
activemq.
You may configure this rededelivery activemq component with name of
rededeliveryActivemq in your spring configuration. Then You can using
different configuration on the ActiveMQConnectionFactory.
O
Christian, great question...I see various forms of this asked many times.
I've considered all the options you mentioned, but for high-volume/critical
messaging scenarios, I struggle with the idea of leaving messages up to the
AMQ config/inflight repositories for lack of control/visibility/testabil
