[
https://issues.apache.org/jira/browse/DERBY-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486048#comment-13486048
]
Rick Hillegas commented on DERBY-5966:
--------------------------------------
The error in question managed to print a complete stack trace for the problem
to *suitesAll.diff.txt:
(emb)lang.NativeAuthenticationServiceTest.testAll
junit.framework.AssertionFailedError: [ FILE, NATIVE authentication on, LOCAL
authentication ON, Authentication/Authorization turned OFF, SecurityManager ON,
Embedded ]: Connection to fifthDB should have failed.
at junit.framework.Assert.fail(Assert.java:47)
at
org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest.getConnection(NativeAuthenticationServiceTest.java:1583)
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)
This indicates that the test was expecting a connection failure by a user whose
password had expired. But the connection succeeded. I can see this situation
arising if clocks change during the test run. There may be a product issue here
but I am not sure how serious it is. Inside Derby, a comparison is being made
between the current time returned by System.currentTimeMillis() and the
contents of a SQL TIMESTAMP stored in SYS.SYSUSERS.LASTMODIFIED. My suspicion
would be that the on-disk and in-memory representations of TIMESTAMPs have some
interesting convertibility behavior during the twilit hour of overlap when the
time zone changes.
> 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
