AMQP Appender does not initiate the channel correctly for confirms about gelfj HOT 3 CLOSED

thats not true, i think it is related to your setup. we are running RabbitMQ 3.2.3 and we do not need to confirmSelect

from gelfj.

regarding waitForConfirms, you can use e.g. an async log4j appender or write an extension to the GelfAMQPSender that does some kind of caching and therefore there is no loss of time

from gelfj.

@h0nIg As for the waitForConfirms I'm using RabbitMQ 3.3.0 (maybe you should upgrade :) ). The latest RabbitMQ client will throw an exception if you call waitForConfirms and the channel is not set for confirmation. You can clearly see this in the javadoc for #waitForConfirms -- Note, when called on a non-Confirm channel, waitForConfirms throws an IllegalStateException.

The log4j async appender will not work correctly MDC context (I tried) and in general the log4j async appender has serious issues and one of the reasons logback, log4j2 and Netflix's blitz4j.

Consequently I gave up and upgraded to log4j2 and use Apache Flume instead of RabbitMQ and Gelf.

from gelfj.