-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Migration Guide 2.13
The Kubernetes Client has been upgraded from 5.12 to 6.1. Please refer to the Kubernetes Client 6 migration guide.
Prior to Quarkus 2.13, the Reactive Messaging consuming methods were called with an active CDI request context, inadvertently propagated, and were never terminated. Quarkus corrects this behaviour and makes sure the request context is not activated unnecessarily on message consuming methods. Code relying on the presence of the RequestScoped
beans might need to start a request scope explicitly; for example, using @ActivateRequestContext
annotation on the message consuming method.
Note that using @ActivateRequestContext
on a method creates a request context if the method is not already called on an existing request context. If a new context was created for the method, at the end of the method execution (e.g. the completion of the returned Uni
or CompletionStage
) the context will be destroyed, effectively disposing request scoped beans bound to it.