On 4 June 2014 at 00:43:52, Brian Marick (br...@getset.com) wrote: > > So what I'd like is for the Clojure apps to System/exit upon that > exception. But it's swallowed (and printed) by beginAutomaticRecovery > in Connection.java. > > Is the only option to hand-roll non-automatic recovery?
All uncaught exceptions are eventually routed to ExceptionHandler (one per connection). Default exception handler prints them out: http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.3.1/rabbitmq-java-client-javadoc-3.3.1/com/rabbitmq/client/ExceptionHandler.html http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.3.1/rabbitmq-java-client-javadoc-3.3.1/com/rabbitmq/client/impl/DefaultExceptionHandler.html RabbitMQ Java client can use any exception handler you want but Langohr does not provide a way to configure it yet: http://www.rabbitmq.com/releases/rabbitmq-java-client/v3.3.1/rabbitmq-java-client-javadoc-3.3.1/com/rabbitmq/client/ConnectionFactory.html#setExceptionHandler(com.rabbitmq.client.ExceptionHandler) Feel free to contribute this feature: https://github.com/michaelklishin/langohr/issues/47 -- MK Software Engineer, Pivotal/RabbitMQ -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
