java.rmi.MarshalException：通信失败
我正在使用 jbossIDE Eclipse 1.6。部署我的 .ear 应用程序时，我收到 java.rmi.MarshalException。
令人惊讶的是，就在几分钟前，一切都还好。
感觉jbossIDE Eclipse这个东西实在是没什么用。它一直在崩溃。
java.rmi.MarshalException: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
java.io.InvalidClassException: com.afrikbrain.util.message.MessageInfo; local class
incompatible: stream classdesc serialVersionUID = 2285009932770474121, local class
serialVersionUID = -2900394430145132451
at
org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:644)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
I'm using jbossIDE Eclipse 1.6. when deploying my .ear app, I get a java.rmi.MarshalException.
what's surprising is that just a few min ago, everything was OK.
I feel like this jbossIDE Eclipse thing is really useless. it's crashing all the time.
java.rmi.MarshalException: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
java.io.InvalidClassException: com.afrikbrain.util.message.MessageInfo; local class
incompatible: stream classdesc serialVersionUID = 2285009932770474121, local class
serialVersionUID = -2900394430145132451
at
org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:644)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
部署到 EJB 服务器的
com.afrikbrain.util.message.MessageInfo类的版本与客户端中的版本不同。这就是为什么它们有不同的序列 ID。尝试删除并重新编译所有内容，以便在服务器和客户端上部署完全相同的类版本。The version of the class
com.afrikbrain.util.message.MessageInfothat is deployed to your EJB server is different from the one in your client. That is why they have different serial IDs. Try removing and re-compiling everything so that you have exactly the same version of the class deployed on both the server and client.