Including sleuth with resilence4j circuit breaker causes package protected getter to return null

[spencergibb]

https://gist.github.com/snicoll/cd93c6e089aadd55089f58df8086a1d5

git clone https://github.com/snicoll/spring-petclinic-microservices.git
cd spring-petclinic-microservices
git checkout wavefront
./mvnw clean install
IMPORTANT: do not use the docker stuff as it’s going to create an account for each service since it doesn’t read the token from your home directory. My docker-fu is too low to fix that
You need to run spring-petclinic-config-server first. Then run spring-petclinic-discovery-server. Once those two are up and running you can run the other ones.

Then change to Hoxton.SR4 and run gateway

[spencergibb]

/cc @snicoll @ryanjbaxter

[marcingrzejszczak]

So this is fixed via spring-cloud/spring-cloud-circuitbreaker@285e6fa ?

[ryanjbaxter]

I believe so

[snicoll]

That commit rather eliminates the issue from happening as far as I can see. The original cause is still there for any other candidate that would have a package protected method.

[spencergibb]

yes, there is still a problem

[marcingrzejszczak]

Is this still an issue? I've managed to run the API gateway only with connection refused exception for Hoxton.SR7 and latest Boot.

[snicoll]

@marcingrzejszczak I think so as we've indicated right above your comment. Resilience4j has nothing to do with the problem, it just happens to exhibit the problem when beans are proxied. To reproduce, you could remove the fix made in Resilience4j and try again.