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] [Commented] (DERBY-5966) NativeAuthenticationServiceTest.testAll() failure: [ FILE, NATIVE authentication on, LOCAL authentication ON, Authentication/Authorization turned OFF, SecurityManager ON, Embedded ]: Connection to fifthDB unexpectedly failed.
Date Tue, 30 Oct 2012 13:14:12 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486854#comment-13486854
] 

Knut Anders Hatlen commented on DERBY-5966:
-------------------------------------------

That sounds right. I'd guess it's similar to DERBY-5964, where a timestamp is stored in the
local time zone in the database. Since Derby doesn't store the time zone alongside the timestamp,
the timestamps are ambiguous around the time the time zone changes, and they may come out
one hour off when they are read from the database.

I suppose that in most cases it doesn't matter much if a password expires one hour too soon
or too late, as the password lifetime would be significantly longer than that. However, derby.authentication.native.passwordLifetimeMillis
allows specification of password expiry with millisecond granularity, so one cannot completely
rule out the possibility that some applications use sub-hour password expiry.
                
> NativeAuthenticationServiceTest.testAll() failure: [ FILE, NATIVE authentication on,
LOCAL authentication ON, Authentication/Authorization turned OFF, SecurityManager ON, Embedded
]: Connection to fifthDB unexpectedly failed.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5966
>                 URL: https://issues.apache.org/jira/browse/DERBY-5966
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.10.0.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> Saw these failures on multiple platforms around the time Europe switched from DST:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/sles/1402814-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/sparc/1402814-suitesAll_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/vista/1402814-suitesAll_diff.txt
> 3) testAll(org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest)junit.framework.AssertionFailedError:
[ FILE, NATIVE authentication on, LOCAL authentication ON, Authentication/Authorization turned
OFF, SecurityManager ON, Embedded ]: Connection to fifthDB unexpectedly failed.
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1604)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1570)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1564)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.vetPasswordLifetime(NativeAuthenticationServiceTest.java:1385)
> 	at org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.testAll(NativeAuthenticationServiceTest.java:618)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

--
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