[jboss-jira] [JBoss JIRA] Closed: (JBREM-1028) JavaSerializationManager should clear ObjectOutputStream internal tables
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Tue Sep 9 02:38:38 EDT 2008
[ https://jira.jboss.org/jira/browse/JBREM-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Sigal closed JBREM-1028.
----------------------------
Resolution: Done
>From Andrew Lee Rubinger in the associated forum:
"The new JAR attached to the JIRA definitely cleans up the held reference in the ObjectOutputStream, as verified by Profiling the heap."
There is a remaining transient failure which will be investigated further.
> 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.5.0.GA (Flounder)
>
>
> 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
More information about the jboss-jira
mailing list