[
https://issues.apache.org/jira/browse/DERBY-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578892#action_12578892
]
Kathey Marsden commented on DERBY-3534:
---------------------------------------
Back to testing with the unchanged jars.
The test complaining about the authentication failure is SecureServerTest.
which does have authentication enabled, but I noticed something strange. When
I run the test it prints
the authentication error and hangs with the trace below printed to the console:
[EMAIL PROTECTED]:~/compattest/test> rju.ksh derbynet.SecureServerTest
..java.sql.SQLException: Connection authentication failure occurred. Reason:
Invalid authentication..
at
org.apache.derby.impl.drda.NetworkServerControlImpl.throwSQLException(NetworkServerControlImpl.java:3279)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java:3216)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java:1836)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.wrapSQLError(NetworkServerControlImpl.java:3794)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2760)
at
org.apache.derby.impl.drda.NetworkServerControlImpl.shutdown(NetworkServerControlImpl.java:1005)
at
org.apache.derby.drda.NetworkServerControl.shutdown(NetworkServerControl.java:384)
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.tearDown(NetworkServerTestSetup.java:265)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at junit.textui.TestRunner.start(TestRunner.java:172)
at junit.textui.TestRunner.main(TestRunner.java:138)
I then tried to bring the server down manually with:
[EMAIL PROTECTED]:~/compattest> java org.apache.derby.drda.NetworkServerControl
shutdown -user MARY -password marypwd
It tells me happily that my server is down, but that's not true. My test is
still hung and if I print a stack dump I see that my network server is still
started. I can ping it as well.
I think there is a bug here. Perhaps I need to have permissions in my policy
file, but
regardless it shouldn't have told me my server was down when it wasn't. I'll
try to get
a repro outside the harness.
> Run 10.3 tests against 10.4 to help identify any compatibility issues
> ---------------------------------------------------------------------
>
> Key: DERBY-3534
> URL: https://issues.apache.org/jira/browse/DERBY-3534
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3534_changes_for_running_tests_DO_NOT_COMMIT.txt,
> rjall.out
>
>
> It would be good to run the 10.3 tests against 10.4 to identify any compat
> issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
