db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6285) Use factory method to create thread pool for timed login
Date Wed, 03 Jul 2013 08:44:20 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen resolved DERBY-6285.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
    Issue & fix info:   (was: Patch Available)
    
> Use factory method to create thread pool for timed login
> --------------------------------------------------------
>
>                 Key: DERBY-6285
>                 URL: https://issues.apache.org/jira/browse/DERBY-6285
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.10.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>             Fix For: 10.11.0.0
>
>         Attachments: derby-6285-1a.diff
>
>
> InternalDriver creates a thread pool for running timed logins like this:
>     private static final ThreadPoolExecutor _executorPool =
>             new ThreadPoolExecutor(0, Integer.MAX_VALUE, 60L, TimeUnit.SECONDS,
>                                    new SynchronousQueue<Runnable>());
>     static {
>         _executorPool.setThreadFactory(new DaemonThreadFactory());
>     }
> The java.util.concurrent.Executors class has factory methods that create thread pools
and hide the details such as choosing keep-alive time and which kind of queue to use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message