You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/07/03 10:34:20 UTC
[jira] [Commented] (DERBY-6285) Use factory method to create thread
pool for timed login
[ https://issues.apache.org/jira/browse/DERBY-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698747#comment-13698747 ]
ASF subversion and git services commented on DERBY-6285:
--------------------------------------------------------
Commit 1499257 from [~knutanders]
[ https://svn.apache.org/r1499257 ]
DERBY-6285: Use factory method to create thread pool for timed login
> 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
> 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