Serialization problem using JBossSerialization

[koebbingd]

Using JBossObjectOutputStream and JBossObjectInputStream results in an EOFException.
The main problem is that trying to call an EJB3-method on a bean in another EAR on a jboss server (jboss as 5.1) results in an IOException:

at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:79)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:79)
at org.jboss.ejb3.EJBContainer.invokeCallback(EJBContainer.java:1119)
... 66 more
Caused by: java.io.IOException: field code 0 is not supposed to be on the wire
at com.typesafe.config.impl.SerializedConfigValue.readCode(SerializedConfigValue.java:414)
at com.typesafe.config.impl.SerializedConfigValue.readOrigin(SerializedConfigValue.java:218)
at com.typesafe.config.impl.SerializedConfigValue.readValue(SerializedConfigValue.java:392)
at com.typesafe.config.impl.SerializedConfigValue.readExternal(SerializedConfigValue.java:453)
at org.jboss.serial.persister.ExternalizePersister.readData(ExternalizePersister.java:72)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
at org.jboss.serial.io.MarshalledObjectForLocalCalls.get(MarshalledObjectForLocalCalls.java:60)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:101)
at org.jboss.ejb3.remoting.ClusteredIsLocalInterceptor.invoke(ClusteredIsLocalInterceptor.java:52)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy1483.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
... 80 more

Unfortunately I haven't been able to figure out exactly why the exception occurs.
Using a newer version of jboss-serialization is no solution...

[havocp]

If you can narrow it down to a problem with the config lib and give me a test case, I can look at it. It looks more likely to be a bug in jboss though?

[koebbingd]

Normal (complex) classes can be serialized/deserialized with JBoss-serialization so I gather it's a problem with the way the config library handles it.
Btw.: config is a great lib!

[havocp]

We are using writeReplace(), which is part of how Java serialization works, but if JBoss is reimplementing serialization or something like that, maybe they didn't handle it correctly? It isn't a commonly-used feature perhaps. I don't know anything about what jboss might be doing here so I'm just speculating.

[havocp]

I'm not sure how to make progress here without a test case, but willing to look at it if someone can help me pin it down.