You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Bobby Lawrence <ro...@jlab.org> on 2005/06/01 00:01:02 UTC
Incompatible class Exception
I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
java.io.InvalidClassException: org.apache.ojb.broker.util.collections.RemovalAwareCollection; local class incompatible: stream classdesc serialVersionUID = -7915096023416965226, local class serialVersionUID = 6853709708973269593
What is going on here?
I have turned on debugging, and I get the following preceeding the
exception:
DEBUG cache.MaterializationCache - Materialisation of object is finished, push 16objects to cache
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Person{5346}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.PI{5346,2545}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.SystemResource{68}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Science{303}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Project{2544}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Person{5345}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Grant{2544,fhdf,1761}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Project{2545}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.InciteRequest{745}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Lab{ORNL}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.SystemResource{65}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Organization{1763}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Allocation{2544,zxcv,65}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.Organization{1761}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.PersonsEmail{5345,bobby@aol.com}
DEBUG cache.MaterializationCache - Push to cache: org.jlab.mis.apps.mics.valueobjects.InciteRequest{744}
DEBUG cache.MaterializationCache - Clear materialization cache
DEBUG core.PersistenceBrokerImpl - PB.close was called: org.apache.ojb.broker.core.PersistenceBrokerImpl@6019b76
DEBUG cache.MaterializationCache - Clear materialization cache
It looks like OJB can get all my object correctly, but something happens
right after the caching.
Weird.
I have a web application that makes calls to a remote session bean that
handles all my OJB stuff...
I have NOT changed my OJB.properties file, could this have something to
do with it?
I have verified that there is NO earlier version of OJB in my
classpath.....any ideas?
--
----------------------------
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robertl@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Bobby Lawrence <ro...@jlab.org>.
Well -
Here is the catch-all....my java objects don't even use collections!
They are using arrays.
I have not gotten the chance to upgrade them to Collections yet.
Armin Waibel wrote:
> Bobby Lawrence wrote:
>
>> Well -
>> The OJB jar is not in the web-app classpath.
>> I have the jar in the EJB classpath.
>> I have removed it and I get the desired effect...the app server can't
>> find the PersistenceBroker class.
>> When I use ANY version of > 1.0.1, I get this exception.
>> --Bobby
>>
>
> you mentioned that you use a remote session bean, so your client need
> org.apache.ojb.broker.util.collections.RemovalAwareCollection
> class in classpath too, because the serialized objects with 1:n
> references use this class to store the referenced objects. How does
> your webApp get access to this class? Maybe you put only this class
> object in the classpath of your webApp.
>
> regards,
> Armin
>
>
>> Armin Waibel wrote:
>>
>>> Hi Bobby,
>>>
>>> Bobby Lawrence wrote:
>>>
>>>> OK - After upgrading to 1.0.3 and the newer version of the
>>>> OJB.properties file, I am still getting the exception:
>>>>
>>>> java.io.InvalidClassException:
>>>> org.apache.ojb.broker.util.collections.RemovalAwareCollection;
>>>> local class incompatible: stream classdesc serialVersionUID =
>>>> -7915096023416965226, local class serialVersionUID =
>>>> 6853709708973269593
>>>> at
>>>> java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundException;Ljava.io.ObjectStreamClass;)V(Unknown
>>>> Source)
>>>
>>>
>>>
>>>
>>> strange, seems that you have two different versions of class
>>> org.apache.ojb.broker.util.collections.RemovalAwareCollection
>>> in your classpath (this is what the exception asserted).
>>> Are you really sure that both OJB jars (web-app and appServer) are
>>> the same? Could it be the case that the webApp or the appServer use
>>> some kind of "jar-cache" that still use an outdated jar?
>>>
>>> regards,
>>> Armin
>>>
>>>
>>>
>>>> at
>>>> java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>>>> Source)
>>>> at
>>>> java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>>>> Source)
>>>> at
>>>> java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown
>>>> Source)
>>>> at
>>>> java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown
>>>> Source)
>>>> at
>>>> java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown
>>>> Source)
>>>> at
>>>> weblogic.rmi.internal.CBVInputStream.readObjectInternal()Ljava.lang.Object;(CBVInputStream.java:67)
>>>>
>>>> at
>>>> weblogic.rmi.internal.CBVInputStream.readObject()Ljava.lang.Object;(CBVInputStream.java:61)
>>>>
>>>> at
>>>> weblogic.rmi.internal.ServerRequest.unmarshalReturn()Ljava.lang.Object;(ServerRequest.java:97)
>>>>
>>>>
>>>> Any other ideas?
>>>> --Bobby
>>>>
>>>>
>>>> Martin Kalén wrote:
>>>>
>>>>> Bobby Lawrence wrote:
>>>>>
>>>>>> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>>>>>>
>>>>>> java.io.InvalidClassException:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> <snip/>
>>>>>
>>>>>> I have NOT changed my OJB.properties file, could this have
>>>>>> something to do with it?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Without looking to deeply into the stacktrace you sent;
>>>>> it is always recommended to upgrade OJB.properties and repository
>>>>> between releases. Please diff your old property file against the
>>>>> reference version from 1.0.3 and check if you need to adjust
>>>>> anything.
>>>>>
>>>>> For 1.0.1 => 1.0.3 this is especially true if you are using the
>>>>> ODMG API.
>>>>>
>>>>> (Also not the required change of auto-* repository settings
>>>>> for ODMG in v1.0.3 -- see repository.dtd for full details.)
>>>>>
>>>>> Regards,
>>>>> Martin
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>>>>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
--
----------------------------
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robertl@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Bobby Lawrence <ro...@jlab.org>.
Yes.
The Struts actions in my web-app lookup my session bean, and pass my
objects.
The session bean methods open a PersistenceBroker, do the store/delete
and closes it.
Therefore, I don't even need OJB in my web-app classpath.
And currently, my 1:n references are implemented w/ Arrays...I haven't
gotten the chance to upgrade to Collections...
--B
Martin Kalén wrote:
> Armin Waibel wrote:
>
>>> Well -
>>> The OJB jar is not in the web-app classpath.
>>> I have the jar in the EJB classpath.
>>> I have removed it and I get the desired effect...the app server
>>> can't find the PersistenceBroker class.
>>> When I use ANY version of > 1.0.1, I get this exception.
>>
>>
>> you mentioned that you use a remote session bean, so your client need
>> org.apache.ojb.broker.util.collections.RemovalAwareCollection
>> class in classpath too, because the serialized objects with 1:n
>> references use this class to store the referenced objects. How does
>> your webApp get access to this class? Maybe you put only this class
>> object in the classpath of your webApp.
>
>
> Could it be that both ends does indeed (through EJB classpath) have
> access to the same JAR, but RemovalAwareCollection is missing a
> serialVersionUID declaration and therefore deserialization by the
> JVM on the recieving end gives another SUID than
> when it loads the class on the server end?
>
> Is it the same JVM/JRE on both ends? If so, my answer does probably
> *not* apply (since the SUID should then be calculated to the
> same number regardless on how it was loaded).
>
> Regards,
> Martin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
--
----------------------------
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robertl@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Martin Kalén <mk...@apache.org>.
Armin Waibel wrote:
>> Well -
>> The OJB jar is not in the web-app classpath.
>> I have the jar in the EJB classpath.
>> I have removed it and I get the desired effect...the app server can't
>> find the PersistenceBroker class.
>> When I use ANY version of > 1.0.1, I get this exception.
>
> you mentioned that you use a remote session bean, so your client need
> org.apache.ojb.broker.util.collections.RemovalAwareCollection
> class in classpath too, because the serialized objects with 1:n
> references use this class to store the referenced objects. How does your
> webApp get access to this class? Maybe you put only this class object in
> the classpath of your webApp.
Could it be that both ends does indeed (through EJB classpath) have
access to the same JAR, but RemovalAwareCollection is missing a
serialVersionUID declaration and therefore deserialization by the
JVM on the recieving end gives another SUID than
when it loads the class on the server end?
Is it the same JVM/JRE on both ends? If so, my answer does probably
*not* apply (since the SUID should then be calculated to the
same number regardless on how it was loaded).
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Armin Waibel <ar...@apache.org>.
Bobby Lawrence wrote:
> Well -
> The OJB jar is not in the web-app classpath.
> I have the jar in the EJB classpath.
> I have removed it and I get the desired effect...the app server can't
> find the PersistenceBroker class.
> When I use ANY version of > 1.0.1, I get this exception.
> --Bobby
>
you mentioned that you use a remote session bean, so your client need
org.apache.ojb.broker.util.collections.RemovalAwareCollection
class in classpath too, because the serialized objects with 1:n
references use this class to store the referenced objects. How does your
webApp get access to this class? Maybe you put only this class object in
the classpath of your webApp.
regards,
Armin
> Armin Waibel wrote:
>
>> Hi Bobby,
>>
>> Bobby Lawrence wrote:
>>
>>> OK - After upgrading to 1.0.3 and the newer version of the
>>> OJB.properties file, I am still getting the exception:
>>>
>>> java.io.InvalidClassException:
>>> org.apache.ojb.broker.util.collections.RemovalAwareCollection; local
>>> class incompatible: stream classdesc serialVersionUID =
>>> -7915096023416965226, local class serialVersionUID = 6853709708973269593
>>> at
>>> java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundException;Ljava.io.ObjectStreamClass;)V(Unknown
>>> Source)
>>
>>
>>
>> strange, seems that you have two different versions of class
>> org.apache.ojb.broker.util.collections.RemovalAwareCollection
>> in your classpath (this is what the exception asserted).
>> Are you really sure that both OJB jars (web-app and appServer) are the
>> same? Could it be the case that the webApp or the appServer use some
>> kind of "jar-cache" that still use an outdated jar?
>>
>> regards,
>> Armin
>>
>>
>>
>>> at
>>> java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>>> Source)
>>> at
>>> java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>>> Source)
>>> at
>>> java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown
>>> Source)
>>> at
>>> java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown
>>> Source)
>>> at
>>> java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
>>> at
>>> weblogic.rmi.internal.CBVInputStream.readObjectInternal()Ljava.lang.Object;(CBVInputStream.java:67)
>>>
>>> at
>>> weblogic.rmi.internal.CBVInputStream.readObject()Ljava.lang.Object;(CBVInputStream.java:61)
>>>
>>> at
>>> weblogic.rmi.internal.ServerRequest.unmarshalReturn()Ljava.lang.Object;(ServerRequest.java:97)
>>>
>>>
>>> Any other ideas?
>>> --Bobby
>>>
>>>
>>> Martin Kalén wrote:
>>>
>>>> Bobby Lawrence wrote:
>>>>
>>>>> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>>>>>
>>>>> java.io.InvalidClassException:
>>>>
>>>>
>>>>
>>>>
>>>> <snip/>
>>>>
>>>>> I have NOT changed my OJB.properties file, could this have
>>>>> something to do with it?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Without looking to deeply into the stacktrace you sent;
>>>> it is always recommended to upgrade OJB.properties and repository
>>>> between releases. Please diff your old property file against the
>>>> reference version from 1.0.3 and check if you need to adjust anything.
>>>>
>>>> For 1.0.1 => 1.0.3 this is especially true if you are using the ODMG
>>>> API.
>>>>
>>>> (Also not the required change of auto-* repository settings
>>>> for ODMG in v1.0.3 -- see repository.dtd for full details.)
>>>>
>>>> Regards,
>>>> Martin
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>>>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Bobby Lawrence <ro...@jlab.org>.
Well -
The OJB jar is not in the web-app classpath.
I have the jar in the EJB classpath.
I have removed it and I get the desired effect...the app server can't
find the PersistenceBroker class.
When I use ANY version of > 1.0.1, I get this exception.
--Bobby
Armin Waibel wrote:
> Hi Bobby,
>
> Bobby Lawrence wrote:
>
>> OK - After upgrading to 1.0.3 and the newer version of the
>> OJB.properties file, I am still getting the exception:
>>
>> java.io.InvalidClassException:
>> org.apache.ojb.broker.util.collections.RemovalAwareCollection; local
>> class incompatible: stream classdesc serialVersionUID =
>> -7915096023416965226, local class serialVersionUID = 6853709708973269593
>> at
>> java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundException;Ljava.io.ObjectStreamClass;)V(Unknown
>> Source)
>
>
> strange, seems that you have two different versions of class
> org.apache.ojb.broker.util.collections.RemovalAwareCollection
> in your classpath (this is what the exception asserted).
> Are you really sure that both OJB jars (web-app and appServer) are the
> same? Could it be the case that the webApp or the appServer use some
> kind of "jar-cache" that still use an outdated jar?
>
> regards,
> Armin
>
>
>
>> at
>> java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>> Source)
>> at
>> java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
>> Source)
>> at
>> java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown
>> Source)
>> at
>> java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown
>> Source)
>> at
>> java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
>> at
>> weblogic.rmi.internal.CBVInputStream.readObjectInternal()Ljava.lang.Object;(CBVInputStream.java:67)
>>
>> at
>> weblogic.rmi.internal.CBVInputStream.readObject()Ljava.lang.Object;(CBVInputStream.java:61)
>>
>> at
>> weblogic.rmi.internal.ServerRequest.unmarshalReturn()Ljava.lang.Object;(ServerRequest.java:97)
>>
>>
>> Any other ideas?
>> --Bobby
>>
>>
>> Martin Kalén wrote:
>>
>>> Bobby Lawrence wrote:
>>>
>>>> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>>>>
>>>> java.io.InvalidClassException:
>>>
>>>
>>>
>>> <snip/>
>>>
>>>> I have NOT changed my OJB.properties file, could this have
>>>> something to do with it?
>>>
>>>
>>>
>>>
>>> Without looking to deeply into the stacktrace you sent;
>>> it is always recommended to upgrade OJB.properties and repository
>>> between releases. Please diff your old property file against the
>>> reference version from 1.0.3 and check if you need to adjust anything.
>>>
>>> For 1.0.1 => 1.0.3 this is especially true if you are using the ODMG
>>> API.
>>>
>>> (Also not the required change of auto-* repository settings
>>> for ODMG in v1.0.3 -- see repository.dtd for full details.)
>>>
>>> Regards,
>>> Martin
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
--
----------------------------
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robertl@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Armin Waibel <ar...@apache.org>.
Hi Bobby,
Bobby Lawrence wrote:
> OK - After upgrading to 1.0.3 and the newer version of the
> OJB.properties file, I am still getting the exception:
>
> java.io.InvalidClassException:
> org.apache.ojb.broker.util.collections.RemovalAwareCollection; local
> class incompatible: stream classdesc serialVersionUID =
> -7915096023416965226, local class serialVersionUID = 6853709708973269593
> at
> java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundException;Ljava.io.ObjectStreamClass;)V(Unknown
> Source)
strange, seems that you have two different versions of class
org.apache.ojb.broker.util.collections.RemovalAwareCollection
in your classpath (this is what the exception asserted).
Are you really sure that both OJB jars (web-app and appServer) are the
same? Could it be the case that the webApp or the appServer use some
kind of "jar-cache" that still use an outdated jar?
regards,
Armin
> at
> java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
> Source)
> at
> java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown
> Source)
> at
> java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown
> Source)
> at
> java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
> at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown
> Source)
> at
> weblogic.rmi.internal.CBVInputStream.readObjectInternal()Ljava.lang.Object;(CBVInputStream.java:67)
>
> at
> weblogic.rmi.internal.CBVInputStream.readObject()Ljava.lang.Object;(CBVInputStream.java:61)
>
> at
> weblogic.rmi.internal.ServerRequest.unmarshalReturn()Ljava.lang.Object;(ServerRequest.java:97)
>
>
> Any other ideas?
> --Bobby
>
>
> Martin Kalén wrote:
>
>> Bobby Lawrence wrote:
>>
>>> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>>>
>>> java.io.InvalidClassException:
>>
>>
>> <snip/>
>>
>>> I have NOT changed my OJB.properties file, could this have something
>>> to do with it?
>>
>>
>>
>> Without looking to deeply into the stacktrace you sent;
>> it is always recommended to upgrade OJB.properties and repository
>> between releases. Please diff your old property file against the
>> reference version from 1.0.3 and check if you need to adjust anything.
>>
>> For 1.0.1 => 1.0.3 this is especially true if you are using the ODMG API.
>>
>> (Also not the required change of auto-* repository settings
>> for ODMG in v1.0.3 -- see repository.dtd for full details.)
>>
>> Regards,
>> Martin
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-user-help@db.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Bobby Lawrence <ro...@jlab.org>.
OK - After upgrading to 1.0.3 and the newer version of the
OJB.properties file, I am still getting the exception:
java.io.InvalidClassException: org.apache.ojb.broker.util.collections.RemovalAwareCollection; local class incompatible: stream classdesc serialVersionUID = -7915096023416965226, local class serialVersionUID = 6853709708973269593
at java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundException;Ljava.io.ObjectStreamClass;)V(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.rmi.internal.CBVInputStream.readObjectInternal()Ljava.lang.Object;(CBVInputStream.java:67)
at weblogic.rmi.internal.CBVInputStream.readObject()Ljava.lang.Object;(CBVInputStream.java:61)
at weblogic.rmi.internal.ServerRequest.unmarshalReturn()Ljava.lang.Object;(ServerRequest.java:97)
Any other ideas?
--Bobby
Martin Kalén wrote:
> Bobby Lawrence wrote:
>
>> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>>
>> java.io.InvalidClassException:
>
> <snip/>
>
>> I have NOT changed my OJB.properties file, could this have something
>> to do with it?
>
>
> Without looking to deeply into the stacktrace you sent;
> it is always recommended to upgrade OJB.properties and repository
> between releases. Please diff your old property file against the
> reference version from 1.0.3 and check if you need to adjust anything.
>
> For 1.0.1 => 1.0.3 this is especially true if you are using the ODMG API.
>
> (Also not the required change of auto-* repository settings
> for ODMG in v1.0.3 -- see repository.dtd for full details.)
>
> Regards,
> Martin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
--
----------------------------
Bobby Lawrence
MIS Application Developer
Jefferson Lab (www.jlab.org)
Email: robertl@jlab.org
Office: (757) 269-5818
Pager: (757) 584-5818
----------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: Incompatible class Exception
Posted by Martin Kalén <mk...@apache.org>.
Bobby Lawrence wrote:
> I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
>
> java.io.InvalidClassException:
<snip/>
> I have NOT changed my OJB.properties file, could this have something to
> do with it?
Without looking to deeply into the stacktrace you sent;
it is always recommended to upgrade OJB.properties and repository
between releases. Please diff your old property file against the
reference version from 1.0.3 and check if you need to adjust anything.
For 1.0.1 => 1.0.3 this is especially true if you are using the ODMG API.
(Also not the required change of auto-* repository settings
for ODMG in v1.0.3 -- see repository.dtd for full details.)
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org