[
https://issues.jboss.org/browse/AS7-4542?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas moved JBPAPP-8761 to AS7-4542:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4542 (was: JBPAPP-8761)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.1.Final
(was: EAP 6.0.0 ER 5)
Component/s: EJB
(was: EJB)
Security: (was: Public)
Fix Version/s: 7.1.2.Final-redhat1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
CLONE - ejbActivate called instead of ejbPassivate for EJB2 stateful
beans
--------------------------------------------------------------------------
Key: AS7-4542
URL:
https://issues.jboss.org/browse/AS7-4542
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Reporter: Ondřej Chaloupka
Assignee: Stuart Douglas
Labels: eap6_need_triage
Fix For: 7.1.2.Final-redhat1
There is problem with passivation of EJB2 stateful bean. Please check my test case:
https://github.com/ochaloup/jboss-as/commit/91459f954225dc2760ae640f91218...
Bean is defined with usage of annotation.
https://github.com/ochaloup/jboss-as/blob/91459f954225dc2760ae640f9121864...
The EJB2 beans are not passivated or ejbPassivate method is not called on passivation
event. There could be problem with definition of cache that is used for passivating of
EJB2 beans. In case that it should be used another configuration than that for ejb3 beans
then this could be only configuration issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira