[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6094:
---------------------------------
Attachment: LoginTimeoutTest.java
Attaching a new version of LoginTimeoutTest. This version shows what Derby does
in the following situations:
1) An embedded app tries to connect after calling
DriverManager.setLoginTimeout() on the embedded VM.
2) A client app tries to connect after someone called
DriverManager.setLoginTimeout() on the server VM.
3) A client app tries to connect after calling DriverManager.setLoginTimeout()
on the client VM.
I believe that in all 3 situations, sluggish logins should result in
java.sql.SQLTimeoutException. The behavior right now is:
(1) and (2): no exception
(3): a java.sql.SQLNonTransientConnectionException
I have coded a candidate solution, but I want to run a battery of tests before
submitting it for community review.
> Derby ignores DriverManager.setLoginTimeout()
> ---------------------------------------------
>
> Key: DERBY-6094
> URL: https://issues.apache.org/jira/browse/DERBY-6094
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Attachments: LoginTimeoutTest.java, LoginTimeoutTest.java,
> LoginTimeoutTest.java
>
>
> If you set a login timeout using the DriverManager, Derby ignores the
> setting. I will attach a test case which shows this.
--
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
