GitHub user gquintana opened a pull request:
https://github.com/apache/camel/pull/144
CAMEL-6869 Support reconnection when broker goes down
- Add Spring DSL test
- Try to fix CAMEL-6869: https://issues.apache.org/jira/browse/CAMEL-6869
When the broker is not available, and Camel starts:
- If Producer starts, the connection will be lazily opened on message
sending
- If Consumer starts, a background task is started, waiting to register
the message listener as soon as the broker is available
When Camel is started and the broker is stopped, or becomes unavaible:
- Tuning the requestedHeartbeat, networkRecoveryInterval,
automaticRecoveryEnabled on connectionfactory should be enough
Comment if you think the fix is not satisfactory or if you see a better way
to handle broker unavailability.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gquintana/camel
camel-6869-support-reconnection
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/144.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #144
----
commit 0762be7e581fce84e761442b8eb3abfe23be2af1
Author: Gerald Quintana <gerald.quint...@zenika.com>
Date: 2014-05-05T13:43:20Z
RabbitMQ - Spring DSL intégration test
commit 1191e19fc194b545931530011511a55a8d6d6431
Author: Gerald Quintana <gerald.quint...@zenika.com>
Date: 2014-05-05T13:47:01Z
Reconnect RabbitMQ Producer/Consumer after broker was unavailable
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
