Details
Description
If you set a login timeout using the DriverManager, Derby ignores the setting. I will attach a test case which shows this.
Attachments
Attachments
Issue Links
- breaks
-
DERBY-6122 InterruptResilienceTest fails with: junit.framework.ComparisonFailure: Database shutdown expected:<[08006]> but was:<[XBDA0]>
- Closed
- is related to
-
DERBY-6107 Investigate why setting a login timeout causes NativeAuthenticationServiceTest to fail when run in a suite
- Closed
-
DERBY-6167 Interrupt restarts clock for login timeout
- Closed
- relates to
-
DERBY-2026 Setting a login timeout in client driver can lead to query timeout
- Closed
-
DERBY-6000 Implement support for JDBC 4.2
- Closed