[
https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin...
]
Scott Marlow commented on WFLY-12777:
-------------------------------------
[~cfang] it seems like we are always hitting this during our Jakarta EE 8 TCK platform
runs, so I think this should be a blocking issue. I'll update.
CC: [~bstansberry2]
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}
Or the stateful bean timeout can be configured with ejb-jar.xml:
{code:xml}
<session>
<ejb-name>xx</ejb-name>
<business-local>xx</business-local>
<ejb-class>xx</ejb-class>
<session-type>Stateful</session-type>
<stateful-timeout>
<timeout>-1</timeout>
<unit>Days</unit>
</stateful-timeout>
<concurrency-management-type>Container</concurrency-management-type>
</session>
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)