Red Hat Bugzilla – Bug 1268424
[GSS](6.4.z) SFSB infinite loop if Passivate fails
Last modified: 2017-01-17 06:42:54 EST
If a Stateful Session Bean is accessed and then goes into passivation and an exception occurs, the next call to get the SFSB gets stuck in an infinite loop looking for the SFSB key in this class:
It appears PassivateTask is scheduled with a thread pool, it attempts the passivation and logs the exception that occurs, but the SFSB key does not appear to be removed when passivation fails, this results in the infinite loop above.
I presume this is free to take Brad?
If a SFSB fails to passivate it should not be destroyed. (Though this is allowed by spec.)
This might become a configuration option in the future.
Thus bug is purely about the infinite loop that occurs.
In the end I decided not to destroy the bean but call postActivate() and leave it active instead. Asked Paul for review.
Tomas Hofman <firstname.lastname@example.org> updated the status of jira WFLY-5496 to Coding In Progress
Verified with EAP 6.4.5.CR1.
The newly added PassivationSucceedsUnitTestCase fails intermittently, there will be a separate BZ to resolve it.
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.