[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-952) Not able to access EJB3 from client running in jre1.6, while it works if client running in jre1.5

[Harsha setty (JIRA)]

Not able to access EJB3 from client running in jre1.6, while it works if client running in jre1.5
-------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-952
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-952
             Project: EJB 3.0
          Issue Type: Bug
         Environment: JBOSS 4.0.5 GA with EJB3 profile, EJBs - JBOSS running in JRE1.6 and EJBs compiled in JDK1.6. Works well with Client with JRE1.5 but throws "socket corrupted exception" for JRE1.6

This errors appear both on JBOSS installed on Windows XP and Red Hat Linux.
            Reporter: Harsha setty
            Priority: Critical
             Fix For: EJB 3.0 RC9 - FD


When my java client runs in JRE1.6, it throws the exception


Exception in thread "main" java.lang.reflect.UndeclaredThrowableException

      at $Proxy0.authenticateUser(Unknown Source)

      at gui.Test.main(Test.java:40)

Caused by: java.rmi.MarshalException: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is: 

      java.io.StreamCorruptedException: invalid type code: 00

      at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306)

      at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)

      at org.jboss.remoting.Client.invoke(Client.java:525)

      at org.jboss.remoting.Client.invoke(Client.java:488)

      at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)

      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)

      at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)

      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)

      at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)

      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)

      at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)

      at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)

      at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)

      ... 2 more

Caused by: java.io.StreamCorruptedException: invalid type code: 00

      at java.io.ObjectInputStream.readObject0(Unknown Source)

      at java.io.ObjectInputStream.readArray(Unknown Source)

      at java.io.ObjectInputStream.readObject0(Unknown Source)

      at java.io.ObjectInputStream.defaultReadFields(Unknown Source)

      at java.io.ObjectInputStream.readSerialData(Unknown Source)

      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)

      at java.io.ObjectInputStream.readObject0(Unknown Source)

      at java.io.ObjectInputStream.readObject(Unknown Source)

      at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:122)

      at java.io.ObjectInputStream.readExternalData(Unknown Source)

      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)

      at java.io.ObjectInputStream.readObject0(Unknown Source)

      at java.io.ObjectInputStream.defaultReadFields(Unknown Source)

      at java.io.ObjectInputStream.readSerialData(Unknown Source)

      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)

      at java.io.ObjectInputStream.readObject0(Unknown Source)

      at java.io.ObjectInputStream.readObject(Unknown Source)

      at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)

      at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)

      at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)

      ... 14 more



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira