Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoteAccessException does not have the serialVersionUID defined [SPR-4826] #9502

Closed
spring-projects-issues opened this issue May 15, 2008 · 1 comment
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Gabriel Rosu opened SPR-4826 and commented

Having two tiers of the application on two physical boxes running SunOS 5.10 and sun's JDK 1.4.2_13 we're running into a deserializing problem when one of them throws an exception against the other. Here's the stacktrace:

2008-05-01 00:05:06,158 ERROR [ExecuteThread: '87' for queue: 'weblogic.kernel.Default'] svc.impl.InventorySvcImpl - java.rmi.UnmarshalException: Problem deserializing error response; nested exception is:
java.io.InvalidClassException: org.springframework.remoting.RemoteAccessException; local class incompatible: stream classdesc serialVersionUID = 3787812861223238444, local class serialVersionUID = -4906825139312227864

Note that our embedded exception has the serializeVersionUID set and we have the same version of it on both tiers; also have the same spring 2.0.8 version on both tiers.
We did notice that the RemoteAccessException does not have the serialVersionUID defined and we looked to see if version 2.5 would have that but it's still missing so upgrading spring would not help.


Affects: 2.0.6, 2.0.8

Backported to: 2.0.9

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

This is surprising since if there's the very same version of the Spring RemoteAccessException class on both sides, then the default serialVersionUID calculated by the JDK should be the same - and hence be considered compatible.

In any case, I've declared -4906825139312227864L as explicit UID now, which should be backwards compatible with both Spring 1.2 and 2.0. This will be available as of Spring 2.5.5 and 2.0.9.

Juergen

@spring-projects-issues spring-projects-issues added type: bug A general bug status: backported An issue that has been backported to maintenance branches in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 2.5.5 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants