- 23 Sep, 2015 1 commit
-
-
Dave Syer authored
-
- 22 Sep, 2015 1 commit
-
-
Spencer Gibb authored
Move turbine/hystrix amqp specific implementations to spring-cloud-stream based implementations and let the user decide which broker to use. fixes gh-545
-
- 17 Mar, 2015 1 commit
-
-
Dave Syer authored
-
- 16 Mar, 2015 1 commit
-
-
Dave Syer authored
Fixes gh-259
-
- 27 Feb, 2015 2 commits
-
-
Dave Syer authored
-
Dave Syer authored
If you are using AMQP there needs to be a ConnectionFactory (from Spring Rabbit) in the application context. If there is a single ConnectionFactory it will be used, or if there is a one qualified as @[Hystrix,Turbine]ConnectionFactory it will be preferred over others, otherwise the @Primary one will be used. If there are multiple unqualified connection factories there will be an error. See https://github.com/spring-cloud/spring-cloud-bus/issues/13
-
- 29 Jan, 2015 2 commits
- 26 Jan, 2015 1 commit
-
-
Spencer Gibb authored
fixes gh-179
-
- 22 Jan, 2015 2 commits
-
-
Dave Syer authored
Fixes gh-153
-
Spencer Gibb authored
fixes gh-153
-
- 15 Jan, 2015 2 commits
-
-
Spencer Gibb authored
fixes gh-147
-
Dave Syer authored
-
- 14 Jan, 2015 3 commits
-
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
-
- 06 Jan, 2015 1 commit
-
-
Spencer Gibb authored
fixes gh-135 created hystrix.stream.amqp.send-id to allow disabling of sending the context id as the metric id. Turbine AMQP then defaults to serviceId:host:port fixes gh-131
-
- 02 Jan, 2015 1 commit
-
-
Dave Syer authored
Fixes gh-126
-
- 17 Dec, 2014 2 commits
-
-
Spencer Gibb authored
-
Spencer Gibb authored
fixes gh-108
-