java.util.concurrent.ExecutionException

javax.ejb.EJBException: java.io.IOException: Channel Channel ID c51280ed (outbound) of Remoting connection 01e533c6 to /0:0:0:0:0:0:0:1:8080 has been closed

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3358

  • via GitHub by wildfly-ci
    , 11 months ago
    javax.ejb.EJBException: java.io.IOException: Channel Channel ID c51280ed (outbound) of Remoting connection 01e533c6 to /0:0:0:0:0:0:0:1:8080 has been closed
  • via GitHub by wildfly-ci
    , 1 year ago
    javax.ejb.EJBException: java.io.IOException: Channel Channel ID d2619d44 (outbound) of Remoting connection 017b1176 to localhost.localdomain/0:0:0:0:0:0:0:1:8080 has been closed
  • via GitHub by wildfly-ci
    , 11 months ago
    javax.ejb.EJBException: java.io.IOException: Channel Channel ID e6455d3a (outbound) of Remoting connection 493fae9c to /0:0:0:0:0:0:0:1:8080 has been closed
  • Stack trace

    • java.util.concurrent.ExecutionException: javax.ejb.EJBException: java.io.IOException: Channel Channel ID c51280ed (outbound) of Remoting connection 01e533c6 to /0:0:0:0:0:0:0:1:8080 has been closed at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase.testConcurrentFailover(RemoteFailoverTestCase.java:306) Caused by: javax.ejb.EJBException: java.io.IOException: Channel Channel ID c51280ed (outbound) of Remoting connection 01e533c6 to /0:0:0:0:0:0:0:1:8080 has been closed at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:238) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) at com.sun.proxy.$Proxy28.increment(Unknown Source) at org.jboss.as.test.clustering.cluster.ejb.remote.RemoteFailoverTestCase$IncrementTask.run(RemoteFailoverTestCase.java:379) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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) Caused by: java.io.IOException: Channel Channel ID c51280ed (outbound) of Remoting connection 01e533c6 to /0:0:0:0:0:0:0:1:8080 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:514) at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:419) at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:290) at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:543) at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:154) at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleEnd(ChannelAssociation.java:485) at org.jboss.remoting3.remote.RemoteConnectionChannel$2.run(RemoteConnectionChannel.java:286) ... 3 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago