Guillaume Lederrey

@gowa: could you have a look at #566 and see if it resolves your issue?

The circuit breaker should go to [half-open and try again connecting after 1 minute ](https://github.com/jmxtrans/jmxtrans/pull/566/files#diff-a667420575437c9cd9c5c0dc5e74d16eR268) (but honestly, I don't have muc experience with this circuit breaker implementation, so I might...

@gowa I updated the pull request, could you try again? If you could upload the full log somewhere, I'd be interested in having a look...

The numQueryThreads is a left over from an old refactoring. I should clean that up and log a warning if someone tries to use it. At that point, threads were...

Take your time for testing, I'm probably not going to have time to dig further into this before next Monday...

Thanks for the testing! A few comments: > CircuitBreaker itself does not prevent queryProcessorExecutor overflowing: even if the server is responding very fast the size of the configured set of...

Note that if you use `flushStrategy = always`, there is no need to specify a `flushDelay`. `flushDelay` is only used with `timeBased` flush strategy. Yes, I know, documentation is not...

Always flushing is probably not a very good default. It would mean that we send a very small packet with a single metric each time a metric is collected. It...

note: I don't have actual data about this answer, this is mainly guesstimates The increase CPU usage on the new GraphiteWriterFactory is most probably related to the new connection pool...

There is already an [HttpOutputWriter](https://github.com/jmxtrans/jmxtrans/blob/master/jmxtrans-output/jmxtrans-output-core/src/main/java/com/googlecode/jmxtrans/model/output/support/HttpOutputWriter.java). It is not directly configureable, but it can be reused to write a simple Java class for whatever format you need. See for example [LibratoWriter2](https://github.com/jmxtrans/jmxtrans/blob/master/jmxtrans-output/jmxtrans-output-core/src/main/java/com/googlecode/jmxtrans/model/output/LibratoWriter2.java)....