Wildfly 8.2.0 : IO exception is received by client when throwing EJB exception from server

[genie1]

Hello all,

I need help to solve exceptions issue:

My session bean throws my defined ejb exception with some error message. The purpose is to catch this exception in client side.

However, everytime the exception is thrown, I receive in client side IO exception. It happens for all kind of that are thrown from server.

Server log

14:26:00,167 ERROR [ejb3] JBAS014250: Could not write method invocation failure for method public abstract void com.allot.nms.catalog.mobile.ejb.MobileControllerInternal.replaceCatalogEntries(java.util.Collection) throws com.allot.nms.catalog.exception.CatalogException on bean named MobileControllerBean for appname NMS modulename catalog distinctname  due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel

       at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102)

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

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

       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

       at java.util.concurrent.FutureTask.run(FutureTask.java:266)

       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

       at java.lang.Thread.run(Thread.java:745)

       at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Caused by: java.lang.InterruptedException

       at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)

       at java.util.concurrent.Semaphore.acquire(Semaphore.java:312)

       at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:66)

at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100)

client log:

Caused by: java.io.IOException: Channel Channel ID ddd7dcd1 (outbound) of Remoting connection 12c97f7d to localhost/127.0.0.1:80 has been closed

       at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:123)

       at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:115)

       at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)

       at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)

       at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)

at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)

In Jboss 5 it worked, the problem started after moving to Wildfly 8.

Thank you in advance.

[dmlloyd]

Are you interrupting the EJB thread?  Maybe to cancel an operation that is long-running?

[genie1]

I found out that this is only happening while debugging when I try to throw exception on the fly (to reproduce some bug).

When I compiled the code that throws the same exception, it worked ok and the original exception was caught by client.

Was that exception in debug mode interrupting the EJB thread?

[dmlloyd]

I couldn't know.  Another thought is that maybe the debugger's exception causes an UndeclaredThrowableException or other runtime exception to be thrown.  I can only speculate though.