Greetings:
The only way that I can get AMQ 5.2 to properly route an invalid message to
the DLQ is if I use a Non XA connection and set sessionTransaction=true. We
would prefer to use XA if possible.
Is there a known issue with redelivery policy and XA?
Any help would be appreciated.
Could it be
bsnyder wrote:
>
> Trying to do custom message processing inside of ActiveMQ is by no
> means easy to achieve. Camel is definitely the better solution for
> this type of work.
>
We are seeking a solution to this as well. I will be looking at Camel down
the road , but right now I have two ques
Greetings:
We are currently evaluating ActiveMq 5.x
We are trying to decide between AMQMessageStore and jdbc persistence to
Oracle. The documentation seems to advocate for AMQMessageStore over jdbc.
Our project requires that massages cannot be lost.
What are reasons that I would pick one
Greetings:
We are in the early stages of proofing a messaging solution for our
application.
We have chosen ActiveMQ 5.1 for our initial tests, along with Spring 2.5 and
Java 1.5
In development we currently run our application on Jetty 6.x and Atomikos
3.2.3 for XAtransaction management.
In prod
