jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3248) TimeoutHandler visitor should be extracted into a dedicated class
Date Fri, 02 Mar 2012 14:09:58 GMT
TimeoutHandler visitor should be extracted into a dedicated class

                 Key: JCR-3248
                 URL: https://issues.apache.org/jira/browse/JCR-3248
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
          Components: jackrabbit-core
            Reporter: Alex Parvulescu
            Priority: Minor

This is a minor problem that I've stumbled upon when looking at a memory leak.
It seems that the TimeoutHandler thread runs each second and it uses a custom ElementVisitor
to do its business. By creating a new instance of ElementVisitor each second this creates
some garbage that could be avoided by using a predefined class.

Short story: during a unit test it creates 3x instances each second that have 16 bytes each.
Having a dedicated visitor class creates just 3 instances for the lifespan of the repository.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message