[
https://issues.apache.org/jira/browse/DERBY-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945177#comment-13945177
]
Rick Hillegas commented on DERBY-6107:
--------------------------------------
Thanks for that extra explanation, Knut. So it sounds as though setting the
keepAlive time to 0 will just cause DriverManager.getConnection() to incur the
cost of starting a Thread when login timeouts are enabled. That doesn't sound
like an intolerable expense for implementing login timeouts. I prefer that
expense to granting the extra permissions. And I vote for less complexity:
always set the keepAlive time to 0. Thanks.
> Investigate why setting a login timeout causes
> NativeAuthenticationServiceTest to fail when run in a suite
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6107
> URL: https://issues.apache.org/jira/browse/DERBY-6107
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Assignee: Knut Anders Hatlen
>
> See DERBY-6094 for the details of this problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
