[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1028) JavaSerializationManager should clear ObjectOutputStream internal tables

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12427432#action_12427432 ] 

Ron Sigal commented on JBREM-1028:
----------------------------------

A new class, org.jboss.remoting.serialization.impl.java.ClearableObjectOutputStream has been introduced, which overrides java.io.ObjectOutputStream and exposes the protected method clear(), which cleans out ObjectOutputStream's internal tables.  org.jboss.remoting.serialization.impl.java.sendObjectVersion2_2() calls ClearableObjectOutputStream.clear() after writing an object.

There are no particular unit tests.

> JavaSerializationManager should clear ObjectOutputStream internal tables
> ------------------------------------------------------------------------
>
>                 Key: JBREM-1028
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1028
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.SP1 (Pinto)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.4.0.SP2
>
>
> In changing from socket transport wire format 1 to wire format 2 (and 22), we eliminated the last call to ObjectOutputStream.flush().  It turns out that the internal ObjectOutputSteam tables can hold onto objects and cause leaks.  See EJBTHREE-1442 "Ejb3ClassloaderLeakUnitTestCase failures in AS testsuite" and the related forum discussion for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira