I think you can enable sync send to have the message rollback if the queue is full. http://activemq.apache.org/async-sends.html
Can you post your Camel route? The entire stacktrace. And possible which version of Camel you are using? I think that exception is triggered by Spring JMS, and maybe there is a way we can covey that to the Camel JMS client. On Tue, Oct 25, 2011 at 9:02 PM, mkolakow <[email protected]> wrote: > We are listening to a JMS queue, using camel to process messages, and then > send the message (processed or not) to another JMS queue. We are now at the > point where we are testing error handling. So, here is what we have seen: > > When the user doesn't have permission to write the queue, the message gets > rolled back. This is what we expect. > > Here's the real issue/question: > > The user does have permission, but the destination queue is full. Camel > appears only to log a warning and not throw an exception. The message is > dropped. We expect it to rollback. > > Here is the log message: > > 2011-10-25 13:39:09,878 WARN 'Camel thread #4 - JmsMessageListenerContainer > on message : Setup of JMS message listener invoker failed for destination > 'RECEIVE-QUEUE' - trying to recover. Cause: JMS transaction rolled back; > nested exception is javax.jms.TransactionRolledBackException: Destination > limit exceeded > > Thanks, > Michael Kolakowski > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-only-emits-warning-when-destination-queue-is-full-tp4937347p4937347.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
