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] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0
Date Thu, 18 Dec 2014 22:06:13 GMT

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

Mike Matrigali commented on DERBY-6785:
---------------------------------------

I am still struggling to understand if you are encountering a data problem or a client/server
network problem.

derby should support 10.11.1.1 software accessing a database on disk created by any previous
version of derby software.
It is is not the case that previous versions of derby software can access databases created
by higher levels of the 
software.

There are 2 possible modes which are referred to as soft upgrade or hard upgrade.  The mode
is determined by 
whether your connect statement includes "upgrade=true".

There is a separate compatibility issue concerning derby running in client/server mode.  I
do not think that derby
supports mismatched clients running against mismatched network server installations.   It
sounds like this is what
you are doing but I can't tell for sure.  Need more detail about what the GUI client is doing
to access the databases
on different machines.  

One natural possibility would be there is a source machine with client and 2 target machines
with data.:
1) you start a network server on target machines that accesses the database.  If this is what
you are doing, what    version
    of software is being used there.  
2) you connect using derby in client/server mode from source machine using some version of
the software and
    get a problem in some case.  I think you are saying when client uses 10.11 software is
the problem.  In this
    case what version of software is server on target machine using?



> Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-6785
>                 URL: https://issues.apache.org/jira/browse/DERBY-6785
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.10.2.0
>         Environment: Win 7, Win 8, Mac OSX and Ubuntu 14.04
>            Reporter: tariq rahiman
>             Fix For: 10.11.1.3
>
>         Attachments: derby.log, log.zip
>
>
> I have downloaded 10.11.1.1 and 10.10.2.0 from Apache Derby download and installed them
in 2 separate machines.
> I have a GUI client that connects to the toursdb database of both versions using a JDBC
connection that makes uses of derby.jar, derbyclient.jar and derbynet.jar
> I use the latest JDBC drivers from 10.11.1.1 to connect to both the database versions.
The drivers I make use of are derby.jar, derbyclient.jar and derbynet.jar
> Connection to 10.10.2.0 is successful, but when I try to Alter/Drop Tables and Views,
Create an Index or try to retrieve column information of tables, i get the below exception:
> The classpath settings for the two environments are identical and If i replace the derby.jar,
derbyclient.jar and derbynet.jar of the latest release with the 10.10.2.0 ones, it works fine
with 10.10.2.0. 
> So my question is backward compatibility of the latest Apache Derby JDBC drivers. Can
I use 10.11.1.1 jars to connect to 10.10.2.0 ?
> Exception:
> java.sql.SQLException: Error marshalling or unmarshalling a user defined type: org.apache.derby.catalog.types.TypeDescriptorImpl;
local class incompatible: stream classdesc serialVersionUID = -5485274209578709396, local
class serialVersionUID = -3812847726962874375
> 	at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.ClientResultSet.getString(Unknown Source)
> 	at \\...\\ .\\हिñçêČάй語简�?한\\.cꋦᚹ⣞ꊼ 8.a(Unknown Source)
> 	at com.common.ui.tree.eꏷꃒꆶᡰ.a(Unknown Source)
> 	at com.common.ui.tree.eꏷꃒꆶᡰ.wR(Unknown Source)
> 	at com.common.ui.tree.eꏷꃒꆶᡰ$1.process(Unknown Source)
> 	at com.common.ui.util.BackgroundThread.run(Unknown Source)
> Caused by: ERROR XN020: Error marshalling or unmarshalling a user defined type: org.apache.derby.catalog.types.TypeDescriptorImpl;
local class incompatible: stream classdesc serialVersionUID = -5485274209578709396, local
class serialVersionUID = -3812847726962874375
> 	at org.apache.derby.client.am.Cursor.get_UDT(Unknown Source)
> 	at org.apache.derby.client.am.Cursor.getString(Unknown Source)
> 	... 6 more
> Caused by: java.io.InvalidClassException: org.apache.derby.catalog.types.TypeDescriptorImpl;
local class incompatible: stream classdesc serialVersionUID = -5485274209578709396, local
class serialVersionUID = -3812847726962874375
> 	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1622)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> 	... 8 more
> Let me know if you need any more information



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message