Jruby 1.1.7 still leaking weakreferences
----------------------------------------
Key: JRUBY-3238
URL: http://jira.codehaus.org/browse/JRUBY-3238
Project: JRuby
Issue Type: Bug
Components: Java Integration
Affects Versions: JRuby 1.1.7
Environment: Jruby 8302, Glassfish trunk
Reporter: Jacob Kessler
Attachments: JrubyLeakAfter, JrubyLeakBefore
Jruby seems to be leaking a weakreference for each processed request from
Glassfish. This appears to be related to the RC2 hardReference bug, but much
less severe. I've attached jmaps from Glassfish startup and 1.5M requests later
to (hopefully) demonstrate the problem.
I suspect that the issue is that since the GlassFish threads are in a pool,
they don't die and thus Jruby keeps the weakreferences for them lying around,
and creates a new one the next time the thread enters, causing many
weakreferences to the same thread, all of which register as live.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
