[jboss-jira] [JBoss JIRA] Created: (JBCOMMON-119) BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called

James Livingston (JIRA) jira-events at lists.jboss.org
Wed Apr 13 00:33:33 EDT 2011


BasicThreadPool stops using RestoreTCCLThreadPoolExecutor when setMaximumPoolSize is called
-------------------------------------------------------------------------------------------

                 Key: JBCOMMON-119
                 URL: https://issues.jboss.org/browse/JBCOMMON-119
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-core (2.x)
    Affects Versions: 2.2.18.GA 
            Reporter: James Livingston


JBCOMMON-41 modified BasicThreadPool to use a new class RestoreTCCLThreadPoolExecutor, so that the classloader wasn't leaked. However only the code in the constructor was changed, not the code in setMaximumQueueSize() which re-creates the executor.

This means that if you call setMaximumPoolSize(), it will switch back to the standard executor and so the special code in RestoreTCCLThreadPoolExecutor will not run.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list