[
https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin...
]
Cheng Fang commented on WFLY-12777:
-----------------------------------
It could be caused by {{org.jboss.as.ejb3.cache.simple.SimpleCache}} when converting the
stateful timeout vqalue to duration, and therefore incorrectly scheduled it for timeout.
Stateful bean with @StatefulTimeout value -1 should not timeout or
removed
--------------------------------------------------------------------------
Key: WFLY-12777
URL:
https://issues.jboss.org/browse/WFLY-12777
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 19.0.0.Beta1
Reporter: Cheng Fang
Assignee: Cheng Fang
Priority: Major
Fix For: 19.0.0.Beta1
Stateful bean with @StatefulTimeout value -1 should not timeout or removed.
A value of -1 means the bean will never be removed due to timeout. When running with the
latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and
removed.
{code:java}
@Stateful
@StatefulTimeout(value = -1, unit=TimeUnit.DAYS)
@AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS)
@Local(StatefulTimeoutIF.class)
public class Minus1TimeoutBean {
...
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)