7 Replies Latest reply on Jul 2, 2013 7:28 AM by haverland

Message was closed asynchronously by another thread on bigger results

haverland Jun 27, 2013 11:31 AM

I've tested an SessionBean that returns a bigger ArrayList<String>. If the list is to big i got following error on Server (jboss eap 6.1):

59:43,946 ERROR [org.jboss.as.ejb3] (EJB default - 13) JBAS014250: Konnte Fehler beim Aufruf von Methode public abstract java.util.Collection de.ietac.logist

redis2.solldaten.session.interfaces.AuftragSearchHandler.search(java.lang.String[],java.lang.String[],java.lang.String[],int[],java.lang.String[],java.lang.S

ng,java.lang.String,java.lang.String,java.lang.String,boolean,java.util.Date,java.lang.String[],boolean) throws de.ietac.util.ejb.IteratorException,java.rmi.

oteException an Bean namens AuftragSearchHandler f³r Appname redis Modulname redis2lib distinctname nicht schreiben wegen : org.jboss.remoting3.NotOpenExcep

n: Message was closed asynchronously by another thread

at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:116) [jboss-remoting-3.2.16.GA-redhat-1.jar:3.2.16.GA-redhat-1]

at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:126) [xnio-api-3.0.7.GA-redhat-1.jar:3.0.7.GA-redhat-1]

at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:114) [xnio-api-3.0.7.GA-redhat-1.jar:3.0.7.GA-redhat-1]

at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:78) [xnio-api-3.0.7.GA-redhat-1.jar:3.0.7.GA-redhat-1]

at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:96) [xnio-api-3.0.7.GA-redhat-1.jar:3.0.7.GA-redhat-1]

at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:234) [jboss-remoting-3.2.16.GA-redhat-1.jar:3.2.16.GA-redhat-1]

at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_09]

at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler$1.write(AbstractMessageHandler.java:217)

at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56) [jboss-marshalling-1.3.16.GA-redhat-1.jar:1.3.16.GA-redhat-1]

at org.jboss.marshalling.SimpleDataOutput.shallowFlush(SimpleDataOutput.java:328) [jboss-marshalling-1.3.16.GA-redhat-1.jar:1.3.16.GA-redhat-1]

at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:274)

at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:595)

at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62) [jboss-marshalling-1.3.16.GA-redhat-1.jar:1.3.16.GA-redhat-1]

at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119) [jboss-marshalling-1.3.16.GA-redhat-1.jar:1.3.16.GA-redhat-1]

at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:372)

at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$600(MethodInvocationMessageHandler.java:70)

at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:246)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09]

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09]

at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09]

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

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

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

at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]

sed by: an exception which occurred:

in object java.util.ArrayList@1f9e590c

On clientside i got a MessageCancelledException:

java.rmi.RemoteException: Error; nested exception is:

org.jboss.remoting3.MessageCancelledException

at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:234)

at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)

at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)

at $Proxy5.search(Unknown Source)

at de.ietac.logistic.redis2.solldaten.session.client.AuftragSearchHandlerRemote.search(AuftragSearchHandlerRemote.java:74)

at de.ietac.logistic.redis2.solldaten.session.AuftragSearchHandlerTest.testStreetSearch(AuftragSearchHandlerTest.java:199)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)

at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)

at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)

at org.junit.runners.ParentRunner.run(ParentRunner.java:236)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Caused by: org.jboss.remoting3.MessageCancelledException

at org.xnio.streams.BufferPipeInputStream.checkFailure(BufferPipeInputStream.java:280)

at org.xnio.streams.BufferPipeInputStream.read(BufferPipeInputStream.java:171)

at org.jboss.remoting3.remote.InboundMessage$3.read(InboundMessage.java:133)

at java.io.DataInputStream.read(DataInputStream.java:132)

at org.jboss.ejb.client.remoting.ProtocolMessageHandler$1.read(ProtocolMessageHandler.java:105)

at java.io.FilterInputStream.read(FilterInputStream.java:116)

at org.jboss.marshalling.SimpleDataInput.read(SimpleDataInput.java:92)

at org.jboss.marshalling.UTFUtils.readUTFBytes(UTFUtils.java:155)

at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:281)

at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)

at org.jboss.marshalling.river.RiverUnmarshaller.doReadCollectionObject(RiverUnmarshaller.java:180)

at org.jboss.marshalling.river.RiverUnmarshaller.readCollectionData(RiverUnmarshaller.java:772)

at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:649)

at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)

at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37)

at org.jboss.ejb.client.remoting.MethodInvocationResponseHandler$MethodInvocationResultProducer.getResult(MethodInvocationResponseHandler.java:107)

at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:272)

at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocationResult(EJBObjectInterceptor.java:64)

at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:274)

at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocationResult(EJBHomeInterceptor.java:88)

at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:274)

at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:46)

at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:274)

at org.jboss.ejb.client.ReceiverInterceptor.handleInvocationResult(ReceiverInterceptor.java:129)

at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:262)

at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:437)

at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:202)

... 28 more

Caused by: an exception which occurred:

in element at index [38905] of size [48353]

Is where any way to return bigger results or setup an other timeout?

1. Re: Message was closed asynchronously by another thread on bigger results

wdfink Jun 27, 2013 2:40 PM (in response to haverland)

This is a known problem, but I suppose it was prior EAP6.1.
Which version do you use exact?

First you should check whether you have the correct client version (I suppose you have a standalone app) as both sides need to have the correct version (with the patch).

Did you use EAP6.1.FInal and have a subscription?
1 of 1 people found this helpful
Actions
2. Re: Message was closed asynchronously by another thread on bigger results

haverland Jun 28, 2013 3:45 AM (in response to wdfink)

We are trying to change from JBoss AS7.1.3 to JBoss eap 6.1.

It's a test case and runs on JBoss AS7.1.3 ok. But we changed from ejb-remote-client (ejb://) to jndi-remote (remote://).

We don't have a subscription.
Actions
3. Re: Message was closed asynchronously by another thread on bigger results

haverland Jun 28, 2013 4:03 AM (in response to haverland)

I forgot to answer all questions. We are using the 6.1 Final Version and the client-version will be used from the current instance of JBoss.
Actions
4. Re: Message was closed asynchronously by another thread on bigger results

wdfink Jun 28, 2013 4:41 AM (in response to haverland)

Hi Frank,
did you said the test will work with an AS7.1.3(using that client) and fail with EAP6.1.0.Final?
Do you have a simple testcase to share?
Actions
5. Re: Message was closed asynchronously by another thread on bigger results

haverland Jun 28, 2013 4:48 AM (in response to wdfink)

No I meant the JBoss AS71.3 and it's client-lib runs on jenkins with ejb-client fine. We changed it to jndi-remote-client on 6.1.0 Final and it fail. Now I am change back to ejb-remote-client and will post the results.

We never mixed lib's between different versions.
Actions
6. Re: Message was closed asynchronously by another thread on bigger results

wdfink Jun 28, 2013 5:11 AM (in response to haverland)

Both approaches should work.
But there are some differences and confusions.
You might post the reproducer code for both.
Actions
7. Re: Message was closed asynchronously by another thread on bigger results

haverland Jul 2, 2013 7:28 AM (in response to wdfink)

I tried to reproduce it with a static test case, but can't reproduce it.
Actions

Go to original post