db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5932) testAutoNetworkServerBoot fails with Invalid authentication
Date Mon, 15 Apr 2013 17:02:17 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali resolved DERBY-5932.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.11.0.0
                   10.9.2.2
                   10.10.1.2
         Assignee: Mike Matrigali

I believe all the past AutoloadTest failures in 10.9, 10.10, and trunk found in IBM lab test
runs are duplicates of DERBY-6178 where the test did not run properly if a non-default
port was set and test were run concurrently.

If errors are encountered in branches after the fix to DERBY-6178 was applied lets create
new JIRA issues.
                
> testAutoNetworkServerBoot fails with Invalid authentication
> -----------------------------------------------------------
>
>                 Key: DERBY-5932
>                 URL: https://issues.apache.org/jira/browse/DERBY-5932
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.10.1.1
>         Environment: Windows IBM 1.5
>            Reporter: Kathey Marsden
>            Assignee: Mike Matrigali
>              Labels: derby_triage10_10
>             Fix For: 10.10.1.2, 10.9.2.2, 10.11.0.0
>
>         Attachments: d5932test.out
>
>
> I saw this issue in the IBM Nightlies ibm1.6
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1387435-suites.All_diff.txt
> and on 
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1387435-suites.All_diff.txt
> Only on Windows. Linux was fine.  
> 1) testAutoNetworkServerBoot(org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest)java.sql.SQLException:
Connection authentication failure occurred.  Reason: Invalid authentication..
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(Unknown Source)
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(Unknown
Source)
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(Unknown
Source)
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(Unknown Source)
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Unknown Source)
> 	at org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(Unknown Source)
> 	at org.apache.derby.drda.NetworkServerControl.shutdown(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.testAutoNetworkServerBoot(AutoloadTest.java:521)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
> 	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:424)
> 	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:441)

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