[jboss-jira] [JBoss JIRA] (AS7-3505) Strange behaviour of bean passivation with definition of max-size attribute at file-passivation-store
Stuart Douglas (JIRA)
jira-events at lists.jboss.org
Tue Feb 7 00:19:48 EST 2012
[ https://issues.jboss.org/browse/AS7-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart Douglas reassigned AS7-3505:
-----------------------------------
Assignee: Stuart Douglas (was: jaikiran pai)
> Strange behaviour of bean passivation with definition of max-size attribute at file-passivation-store
> -----------------------------------------------------------------------------------------------------
>
> Key: AS7-3505
> URL: https://issues.jboss.org/browse/AS7-3505
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Reporter: Ondřej Chaloupka
> Assignee: Stuart Douglas
> Labels: eap6_prd_req
>
> Please check my test: https://github.com/ochaloup/jboss-as/blob/JBQA-5483-test-migration-passivation2/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/stateful/passivation/PassivationSucceedsUnitTestCase.java
> Bean passivation has strange behavior after definition of max-size for file-passivation-store.
> The test creates two SFSB.
> In case that I set max-size = 1 the passivation was not provided despite it should be because of size of store.
> In case that I set max-size = 2 (or 3) the test freezes. There is no exception but it ends with timeout and no action is provided (the debug log level says: "[com.arjuna.ats.arjuna] (Periodic Recovery) Periodic recovery second pass at Mon, 30 Jan 2012 17:11:29" and continues with messages in similar way)
--
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
More information about the jboss-jira
mailing list