Closed thomaspoignant closed 1 year ago
@thomaspoignant I assume you are using a SDK version <= 1.4.1 ? We had a static field in event handler implementation which caused this. It was fixed with https://github.com/open-feature/java-sdk/pull/545
I will go ahead with the 1.4.2 release - https://github.com/open-feature/java-sdk/pull/527 which contain the fix
Caused by the static event handler usage which was fixed with https://github.com/open-feature/java-sdk/pull/545
Please update SDK version to https://github.com/open-feature/java-sdk/releases/tag/v1.4.2
Yes I was using 1.4.1. Let me try with the new version and I will close the issue.
@Kavindu-Dodan I have the exact same problem with the version v1.4.2
.
@thomaspoignant root cause is the singleton OF API ^1. Once the shutdown is called, eventing mechanism is no longer available.
I will revisit shutdown spec section and fix this
@thomaspoignant Fix is ready and contains your bug recreation code as a test - https://github.com/open-feature/java-sdk/pull/556 :)
@thomaspoignant please update to the newest release v1.4.3 ^1 which contains the fix for this bug
While writing a unit test I found a bug when calling
OpenFeatureAPI.getInstance().shutdown();
and calling backsetProvider()
we have an exception thrown (java.util.concurrent.RejectedExecutionException
).I don't know if this is expected, but this exception is not super explicit anyway.
How to reproduce
The second
setProvider
is throwing this exception: