Multiple invocations of a StatefulSessionBean will end in a infinispan exception if the invocation is from server(SLSB)->server(SFSB).
Here the standalone client contains a loop which invoke the SLSB, the SLSB simple invoke the SFSB on another (clustered)server. The invocation is sticky - so the cluster might not have an effect - and the same SFSB instance is used as expected.
The invocatino fail for the 32. invocation.
If a standalone client invoke the SFSB directly it seems correct working.
It seems that the transaction handling between the server EJB's might be the cause.
- clones
-
JBEAP-10217 [GSS](7.1.0) StatefulSessionBean fail after 31 invocations
- Closed
- is caused by
-
JBTM-2848 Transaction .equals() methods do not comply with specification
- Closed
-
WFLY-8524 OwnableReentrantLock can't recognize two different but equal transaction objects as the same transaction
- Closed
- is related to
-
JBEAP-3432 [QA](7.2.z) IllegalStateException "not in a valid state to be invoking cache operations on" in two cluster test
- Verified
- links to