db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (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 Wed, 31 Oct 2012 15:59:12 GMT

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

Rick Hillegas commented on DERBY-5966:
--------------------------------------

I have logged DERBY-5974, an enhancement for converting all of the TIMESTAMP metadata columns
to TIMESTAMP WITH TIMEZONE (after we implement that datatype). As part of that issue, I suspect
that we would convert all TIMESTAMP metadata to GMT, including SYS.SYSUSERS.LASTMODIFIED.
Until we make that change, I propose that we live with the defect tracked by this bug and
address it with some weasel words in the Reference Manual sections on the password management
procs. Does that seem sufficient? Thanks.

                
> 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