Kai Zander

Are there any updates on this? I bumped into this issue when using `select ... for update` queries on H2. These throw `SQLTimeoutException` when the rows are already locked by...

You shouldn't do stuff like this in a `@PostConstruct` method, bean construction hasn't completely finished at that point and using other beans that might themselves not be fully initialized can...

Our workaround until this is fixed is to manually propagate the context: ```java Flux bufs = ...; Path path = ...; Mono write = Mono.deferContextual(ctx -> DataBufferUtils.write(bufs.contextWrite(ctx), path)); ```

Just encountered the same issue. Looks like `ERROR_ON_FAILURE` currently only works when defining Rules with annotated POJOs using `@Rule(ruleChainAction = RuleChainActionType.ERROR_ON_FAILURE)`. Quite a deal-breaker for me. I'm currently working around...

I've added a comment to one of the changes: https://github.com/spring-projects/spring-data-jpa/commit/1bfc3595ce2e14cdc03decfe350f20e139e3c877#r82897830 This change is preventing me from using AOP to intercept all calls to `EntityManager`.

I just encountered the same issue when the `LoadBalancerClient` is initialized from within an R2DBC transaction (my service is `@Transactional` and performs load-balanced `WebClient` requests with `DeferringLoadBalancerExchangeFilterFunction` as automatically configured...

I stumbled upon this issue as well when trying to implement a js-joda adapter using `Instant` as the model type. I worked around this by modifying the internal state of...

Still an issue for me on 2.31.0. Using `okForJson(object)` fails if the `object` contains `java.time` types with the error `wiremock.com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Java 8 date/time type 'java.time.Instant' not supported by default: add...

> okay.. we have found a workaround/solution maybe maybe this can be verified if this would be a proper way to configure it? > > ```java > @Bean > ReactorNettyHttpClientMapper...

@bclozel Could it make sense to call `Hooks.disableAutomaticContextPropagation()` on context shutdown and/or when `ContextPropagationMode != AUTO`? I was wondering if this particular solution could otherwise impact other Spring Context's running...