New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RabbitMQ Heartbeat and Queue Argument Support #9
Conversation
Switch to Maven + Metrics + SimpleSpec. Thanks, Jarred!
…licy: all) * Added support for specifying a heartbeat on a connection
…licy: all) * Added support for specifying a heartbeat on a connection
- com.rabbitmq.amqp-client from 2.7.1 to 2.8.4 - redis.clients.jedis from 2.0.0. to 2.1.0 - com.googlecode.json-simple.json-simple from 1.1 to 1.1.1 - javax.mail.mail from 1.4.5-rc1 to 1.4.5 - com.yammer.metrics.metrics-core from 2.0.3 to 2.1.2 - com.yammer.metrics.metrics-servlet from 2.0.3 to 2.1.2
- com.rabbitmq.amqp-client from 2.7.1 to 2.8.4 - redis.clients.jedis from 2.0.0. to 2.1.0 - com.googlecode.json-simple.json-simple from 1.1 to 1.1.1 - javax.mail.mail from 1.4.5-rc1 to 1.4.5 - com.yammer.metrics.metrics-core from 2.0.3 to 2.1.2 - com.yammer.metrics.metrics-servlet from 2.0.3 to 2.1.2
Hey Justin, this looks rad - thanks a ton for putting it together! I'll read the diff in full this afternoon. Hope your week's wrapping up well.
|
hey @cscotta, not to rush you or anything, but do you think this might get merged in? Thanks a lot for your work on this framework. It's helped us out tremendously. |
hey @cscotta, is it possible to get this merged in? Thanks a lot. |
ping |
pong 2012/10/18 Justin Plock notifications@github.com
|
Opened a cleaner pull request at #12 |
Allow specifying a heartbeat on the RabbitMQ connection (we connect to RabbitMQ through a load balancer that kills inactive connections). Also allow specifying optional arguments for the RabbitMQ queues (such as x-ha-policy: all).
Also cleaned up some whitespace issues. Sorry for all the pull requests. I had to update the author in some of my commits so they may look a bit messy.
I also just fixed the metrics page to use the default MetricsRegistry so the metrics are properly displayed on the port 1228 status page.