Christian Habermehl

Same result (the affected code didn't change as far as I can see). I attached the updated stack trace (the line numbers of GenericScope.BeanLifecycleWrapper were wrong in the old version):...

I simplified the Class, added some dokumentation and output. Hope now it's clear what happens [RefreshScopeDeadLock-2.0.0.RC2-v2.zip](https://github.com/spring-cloud/spring-cloud-commons/files/2101180/RefreshScopeDeadLock-2.0.0.RC2-v2.zip)

Hi Josh, yes, I use the new parameter (thanks again) from the very beginning. What I did to find some examples is to sum up SearchGoogleAdsStreamResponse.getSerializedSize() for each request. I...

I don't know if it's related but I also had problems with logback and slf4j. spring-boot-dependencies-3.2.2.pom defines logback.version with 1.4.14 and slf4j.version with 2.0.11. But logback-parent-1.4.14.pom defines slf4j.version with 2.0.7....

I think it's a multi-threading issue. I don't know if this class is meant to be accessed by multiple threads simultaneously. I think what is happing here ``` if(xmlNsCache==null) {...

@tomjenkinson You are right. It is possible that the xmlNsCache is initialized twice. But that's not a (big) problem because it's just a cache. The worst thing that could happen...

No, I first tried it with cdk - this failed. Then I tried it via Management Console and this worked. The question regarding the restriction is a good one. When...

I think the best way to avoid the problem would be for the API gateway to accept the x-amz-content-sha256 header. But I don't know where to make this suggestion.

I don't know if it has something to do with the _SIGv4a for REST APIs_-Change in [API Gateway Changelog](https://docs.aws.amazon.com/apigateway/latest/developerguide/history.html), but now my API-Gateway-Requests signed with AwsV4HttpSigner are accepted.