Can you try this against latest nightly build available here https://community.jboss.org/thread/167590. We have fixed some issues in this area recently.

hi!

we use jboss-as-7.1.1.Final and see StreamCorruptedException, too.
did you resolve the issue in the meantime?

we found that StreamCorruptedException is raised when we use Java 1.6 on the server side and Java 1.7 on the client side and ApplicationException is thrown on the server.

the same action with the same ApplicationException as the result does not show StreamCorruptedException when using Java 1.6 on both sides!

we guess it is a bug/ missing feature in org.jboss.marshalling.river.RiverUnmarshaller, because Java 1.7 java.lang.Throwable has field suppressedExceptions that Java 1.6 doesnt have.
what do you think?

regards
robert

robert.geisler wrote:

 

hi!

 

we use jboss-as-7.1.1.Final and see StreamCorruptedException, too.
did you resolve the issue in the meantime?

 

we found that StreamCorruptedException is raised when we use Java 1.6 on the server side and Java 1.7 on the client side and ApplicationException is thrown on the server.

the same action with the same ApplicationException as the result does not show StreamCorruptedException when using Java 1.6 on both sides!

 

we guess it is a bug/ missing feature in org.jboss.marshalling.river.RiverUnmarshaller, because Java 1.7 java.lang.Throwable has field suppressedExceptions that Java 1.6 doesnt have.
what do you think?

 

regards
robert

That's fixed as part of https://issues.jboss.org/browse/EJBCLIENT-46. You can just use 1.0.12.Final version (which contains the fix) of EJB client library on the remote client side to get this fix.

thank you, jaikiran, for the fix and for your instant answer!

jaikiran,

i just tried jboss-ejb-client 1.0.12.Final, but i still get UndeclaredThrowableException/ java.io.StreamCorruptedException.

why? 0: )

i updated jbossall-client.jar and replaced org/jboss/ejb/client/ package by the new version. my ide shows that deprecatedClassTableClasses exists and is set during runtime.

nevertheless StreamCorruptedException get raised in RiverUnmarshaller while readFields of our CustomException object. ProtocolV1ClassTable seems not to be called.

do i have to update jboss-ejb-client library on the server side, too? remember, my server runs on Java 1.6 while remote client uses Java 1.7.

or do i have to update jboss-marshalling-river instead?

regards

robert

EDIT:

just updated JBoss 7 module org.jboss.ejb-client with 1.0.12.Final and it works.

thanks jaikiran!

Sorry, when I suggested that you update only your client classpath, I forgot that the server side EJB client module jar too needs to be updated since the same marshalling ClassTable implementation is used on the server side during marshalling. So you did the right thing by updating even the server side module jar.

hi, jaikiran,

as i told you i updated EJB client module to version 1.0.12.Final.

next step is to install a remoting connection to another JBoss AS Server as shown here: https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance .
i need this to invoke EJBs deployed on a 1st JBoss AS from a WAR within a 2nd JBoss AS.

during deployment of my WAR/ start of JBoss 7.1.1 i get the following error:

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ejb3.dd-based-ejb-client-context."[MYWEBAPP].war": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."[MYWEBAPP].war": Failed to start service

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]

    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]

Caused by: java.lang.AbstractMethodError: org.jboss.as.ejb3.remote.JBossEJBClientXmlConfiguration.getDeploymentNodeSelector()Lorg/jboss/ejb/client/DeploymentNodeSelector;

    at org.jboss.ejb.client.EJBClientContext.<init>(EJBClientContext.java:107)

    at org.jboss.ejb.client.EJBClientContext.create(EJBClientContext.java:172)

    at org.jboss.ejb.client.EJBClientContext.create(EJBClientContext.java:155)

    at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:92)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    ... 3 more

i had a look at the code. EJBClientContext is version 1.0.12.Final and EJBClientConfiguration defines getDeploymentNodeSelector,
but JBossEJBClientXmlConfiguration doesnt implement that because it is version jboss-as-ejb3-7.1.1.Final .

so i need an update to JBossEJBClientXmlConfiguration.

i found version 7.1.2.Final: http://grepcode.com/snapshot/repo1.maven.org/maven2/org.jboss.as/jboss-as-ejb3/7.1.2.Final/ .
but is it save to use 7.1.2.Final when using JBoss 7.1.1.Final?? how am i supposed to update JBossEJBClientXmlConfiguration?

thanks in advance

regards

robert

hi everyone!

after a while i am back to that topic : )

i tried to update module org.jboss.as.ejb3 to jboss-as-ejb3-7.1.2.Final.jar.

as expected it leads to others exceptions, because (newer) dependencies are missing.

next i took a step back: i reinstalled jboss-ejb-client-1.0.5.Final.

to get the fix i replaced org.jboss.ejb.client.remoting.ProtocolV1ClassTable from jboss-ejb-client-1.0.12.Final.
that works for me.

after that i installed a remoting connection to another JBoss AS Server as told before:
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance
now that works, too. no more errors : )

regards
robert