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

Rick Hillegas commented on DERBY-6124:
--------------------------------------

Thanks, Dag. Yes, it's likely that the patch will mask another error. If we 
want to pursue this problem, we need to work from the state of the codeline 
before the patch was applied. Like you and Knut, I don't see where the old 
serialized form came from. It appears to me that the test runs the 
compatibility suite in the vacuous configuration where the client and server 
are both at the current rev level. The closest I have come to an hypothesis 
about this problem is that we've tripped across some odd combination of the 
following:

a) Cruft left over from a previous run of the test on an older Derby version.

b) Creative error swallowing in the schema-bouncing code.

But I haven't been able reproduce this situation.

Maybe the problem will pop up if we run the full compatibility suite with 10.9 
and 10.10 in the list of releases. Thanks.
                
> Marshalling error in JDBCDriverTest as part of CompatibilityTest
> ----------------------------------------------------------------
>
>                 Key: DERBY-6124
>                 URL: https://issues.apache.org/jira/browse/DERBY-6124
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.10.1.1
>         Environment: Java SE 1.7.0-b147, Solaris 11, x86
> --------- Derby Information --------
> [/localhome/tendril4.2/work/run/27358744/jars/sane/derby.jar] 10.10.1.1 - 
> (1458268)
> [/localhome/tendril4.2/work/run/27358744/jars/sane/derbytools.jar] 10.10.1.1 
> - (1458268)
> [/localhome/tendril4.2/work/run/27358744/jars/sane/derbynet.jar] 10.10.1.1 - 
> (1458268)
> [/localhome/tendril4.2/work/run/27358744/jars/sane/derbyclient.jar] 10.10.1.1 
> - (1458268)
>            Reporter: Dag H. Wanvik
>         Attachments: derby-6124-01-aa-givePriceAserialVersionUID.diff
>
>
> Internal Oracle testing of RC 2 testing of 10.10 (Tendril Request 5574239 
> Tendril Task  3614491 ):
> ********* Diff file 
> derbyall/derbynetclientmats/DerbyNetClient/encodingTests/TestEnc.diff
> *** Start: TestEnc jdk1.7.0 DerbyNetClient derbynetclientmats:encodingTests 
> 2013-03-21 14:55:59 ***
> derbyTesting.encoding can only be used with jdk15, skipping test
> *** End:   TestEnc jdk1.7.0 DerbyNetClient derbynetclientmats:encodingTests 
> 2013-03-21 14:55:59 ***
> ********* Diff file 
> derbyall/derbynetclientmats/DerbyNetClient/derbynetclientmats/CompatibilityTest.diff
> *** Start: CompatibilityTest jdk1.7.0 DerbyNetClient 
> derbynetclientmats:derbynetclientmats 2013-03-21 14:55:59 ***
> 0 add
> > .E.
> > There was 1 error:
> > 1) 
> > testJDBCDriver(org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest)java.sql.SQLException:
> >  Error marshalling or unmarshalling a user defined type: 
> > org.apache.derbyTesting.functionTests.tests.lang.Price; local class 
> > incompatible: stream classdesc serialVersionUID = 102726277789621992, local 
> > class serialVersionUID = 1827170030595550895
> > Caused by: org.apache.derby.client.am.SqlException: Error marshalling or 
> > unmarshalling a user defined type: 
> > org.apache.derbyTesting.functionTests.tests.lang.Price; local class 
> > incompatible: stream classdesc serialVersionUID = 102726277789621992, local 
> > class serialVersionUID = 1827170030595550895
> >     ... 22 more
> > Caused by: java.io.InvalidClassException: 
> > org.apache.derbyTesting.functionTests.tests.lang.Price; local class 
> > incompatible: stream classdesc serialVersionUID = 102726277789621992, local 
> > class serialVersionUID = 1827170030595550895
> >     ... 25 more
> > FAILURES!!!
> > Tests run: 2,  Failures: 0,  Errors: 1
> Test Failed.
> *** End:   CompatibilityTest jdk1.7.0 DerbyNetClient 
> derbynetclientmats:derbynetclientmats 2013-03-21
>  14:56:04 ***
> Looking at the Price class I see it doesn't have an explicit 
> serialVersionUID. 

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

Reply via email to