[
https://issues.apache.org/jira/browse/DERBY-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113054#comment-13113054
]
Kathey Marsden commented on DERBY-5209:
---------------------------------------
Using the copied system/wombat database from 10_5SoftupgradeTestOutput.txt , I
did a run (still in soft upgrade mode) with 10.5.3.2 - (1171883)
derbyclient.jar and derbyTesting.jar (first in the classpath) and 10.8.2.1 for
the other jars. I will attach as 0_5SoftUpgradeAnd10_5clientTestOutput.txt.
There were Failures: 202, Errors: 72, most similar to the straight soft
upgrade run.
I have not done a full analysis yet, but filed DERBY-5429 for the incompatible
JVMInfo.class in derbyclient.jar causing an issue triggering JVM dumps.
The only protocol related error I saw was this error:
119)
testConnectShutdownAuthentication(org.apache.derbyTesting.functionTests.tests.jdbcapi.DriverMgrAuthenticationTest)junit.framework.ComparisonFailure:
Unexpected SQL state. expected:<0800[4]> but was:<0800[6]>
Caused by: org.apache.derby.client.am.DisconnectException: Insufficient data
while reading from the network - expected a minimum of 6 bytes and received
only 0 bytes. The connection has been terminated.
I think that is also fallout from DERBY-5429 because the javaDump() method
can't be found we get a serious error on the server side. causing a serious
error server side which leads to the protocol issue.
There were no other protocol issues or hangs which is mostly what I am looking
for in this testing.
> 10.8 upgrade and compatibility testing
> --------------------------------------
>
> Key: DERBY-5209
> URL: https://issues.apache.org/jira/browse/DERBY-5209
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.8.2.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Attachments: 10_5SoftupgradeNotes.txt, 10_5SoftupgradeTestOutput.txt,
> test10_8SoftUpgradeFrom10_5.out
>
>
> I am doing some upgrade, client/server and test compatibility testing with
> 10.8 and am using this issue for tracking tests and results.
> The first test was to create the system/wombat database with 10.5 and run
> Suites.All with 10.8 product jars and 10.5 derbyTesting.jar Then I verified I
> could reconnect with 10.5 and perform a few operations.
> derbyTesting.jar. Environment for reference is:
> export JAVA_HOME="/ibmsvn/ntsoftware/ibm16"
> export PATH="$JAVA_HOME/bin:$PATH"
> LIB="c:/cygwin/home/kmarsden/projects/10.8.1testing/db-derby-10.8.1.2-lib/lib"
> TOOLS="C:/cygwin/svn4/trunka/tools/java"
> LIB_105="C:/cygwin/svnreleases/jars/10.5.3.0"
> export
> CLASSPATH="$LIB/derbyrun.jar;$LIB_105/derbyTesting.jar;$TOOLS/junit.jar;
> TOOLS/jakarta-oro-2.0.8.jar"
> Output attached as test10_8SoftUpgradeFrom10_5.out. There were Failures:
> 188, Errors: 109 which haven't been analyzed yet, but I skimmed them and
> didn't see anything that looked like data corruption.
> Will also run
> 10.7 derbyclient.jar, derbyTesting.jar 10.8 other product jars
> 10.7 derbynet.jar derbyTesting.jar 10.8 other product jars.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
