Hello there!
I've been ill hand haven't seen your replies until now.
Yes, we're usin Oracle AQ.
I have now discovered that since the DB that the queues resides in is not
the same as the one the application operates on we do in fact NOT use
transacted JMS. If I remember correctly it was because
I suppose you use OracleAQ?
We are using this as well but I'm not sure how failed messages are put back
in OracleAQ.
I think I saw that they are put in a kind of DLQ in OracleAQ when the
retries are done.
You should be able to see this by querying in the database.
I don't know whether you are able
Hi Sverre
As Claus said you should use the transactional client, and let OracleAQ
handle the redelivery of failed messages.
You can specify the max_retries and Retry_delay when creating the queue or
topic See oracle docs.
When retries are exhausted OracleAQ will mark the messages as undeliverabl
You can look at transactions so the message is rolled back to the queue.
http://camel.apache.org/transactional-client.html
Mind that if you have a message that keep failing (poison message)
then you need the message broker to move such messages to a dead
letter queue or some sorts so new messages
