Circuit Breaker Service fails to refresh the RabbitMQ change

Products

• Support Only for Spring

Issue/Introduction

When changes are made on the RabbitMQ service tile that alert the DNS or IP, through which RabbitMQ is accessing (e.g. enable load balancer, or adjust number of HAProxy instances), the RabbitMQ connection string in the VCAP_SERVICES environment variable of applications bound to Circuit Breaker service instances will not be refreshed with the change.

This problem only happens to existing Circuit Breaker service instances that were created before changes made to the RabbitMQ service tile.

A restage / rebind / restart the associated leaf apps and Spring Cloud Service (SCS) backing service apps (e.g. turgine-$guid-of-cb-service) does not help. VCAP_SERVICES is still not update with the changed info. There are no issues with newly created Circuit Breaker service.

Resolution

Run the following command to update Circuit Breaker service instance to have the RabbitMQ connection string refreshed.

Note: Replace <CB instance name> with name of Circuit Breaker service instance needs to be updated.

$ cf update-service <CB instance name> -c '{"upgrade": true, "force": true}'