EJBLiteJsfClientBase and EJBLiteClientBase cause ConcurrentModificationException #2402
Description
This challenge is not targeting specification, but the test backend, which can cause ConcurrentModificationException.
This bug was already fixed for TCK11 and TCK12, but the fix is missing in TCK10 - the exception was noticed in one of test executions against GlassFish (7.1.0-SNAPSHOT).
As I already created the PR with the backported fix and merged it (sorry I broke the rules):
- If this challenge would be accepted, there are no further changes required.
- If this challenge would be refused, I already prepared a PR reverting the change: Revert "Defend against intermittent EJB failures" committed and merged in #2396 without correct process #2397 . However merging it would mean that tests depending on the relevant code would fail despite the implementation doesn't break any specification. If I understood well, Open Liberty noticed these failures too.
Additional Context
- See Defend against intermittent EJB failures #2322 for the original fix for TCK11 (and later 12) and stacktraces.
- See Defend against intermittent EJB failures #2396 for my PR backporting the fix.
- See ConcurrentModificationException in TCK 10 specifications#854 for a part of the discussion about this challenge.