[jboss-jira] [JBoss JIRA] (EJBTHREE-2281) SimpleStatefulCache$RemovalTimeoutTask never removes ProxiedStatefullBeanContext
Mirosław Michalski (JIRA)
jira-events at lists.jboss.org
Fri Apr 27 05:02:20 EDT 2012
[ https://issues.jboss.org/browse/EJBTHREE-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688268#comment-12688268 ]
Mirosław Michalski commented on EJBTHREE-2281:
----------------------------------------------
This bug is important for production because it leaks disk space (on my server up to 1GB a day)
> SimpleStatefulCache$RemovalTimeoutTask never removes ProxiedStatefullBeanContext
> --------------------------------------------------------------------------------
>
> Key: EJBTHREE-2281
> URL: https://issues.jboss.org/browse/EJBTHREE-2281
> Project: EJB 3.0
> Issue Type: Bug
> Components: ejb3
> Affects Versions: 1.1.22
> Environment: jboss-as 5.1 patched with latest ejb plugin
> Reporter: Mirosław Michalski
>
> ProxiedStatefulBeanContext doesn't externalize property 'lastUsed' (inherited from StatefulBeanContext), which upon de-externalization gets default value of System.currentTimeMillis().
> This makes SimpleStatefulCache$RemovalTimeoutTask think that this Context has just been used and thus cannot be removed.
> Suggested fix: add 'lastUsed = in.readLong();' to readExternal and 'out.writeLong(lastUsed);' to writeExternal methods of ProxiedStatefulBeanContext
--
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