java.io.IOException

Channel Channel ID fbcc4c7f (outbound) of Remoting connection 0128e61e 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 web19724

  • Channel Channel ID fbcc4c7f (outbound) of Remoting connection 0128e61e to /0:0:0:0:0:0:0:1:8080 has been closed
  • via GitHub by wildfly-ci
    , 11 months ago
    Channel Channel ID fbcc4c7f (outbound) of Remoting connection 0128e61e to /0:0:0:0:0:0:0:1:8080 has been closed
  • via GitHub by wildfly-ci
    , 11 months ago
    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.io.IOException: Channel Channel ID fbcc4c7f (outbound) of Remoting connection 0128e61e to /0:0:0:0:0:0:0:1:8080 has been closed at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:236) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) at com.sun.proxy.$Proxy128.getEJBHome(Unknown Source) at org.jboss.as.test.integration.management.deploy.runtime.StatefulEJBRemoteHomeRuntimeNameTestCase.testStatefulLocalHome(StatefulEJBRemoteHomeRuntimeNameTestCase.java:145) Caused by: java.io.IOException: Channel Channel ID fbcc4c7f (outbound) of Remoting connection 0128e61e 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.closeReadsAndWrites(RemoteConnectionChannel.java:274) at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:236) at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413) at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54) at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:154) at org.jboss.ejb.client.remoting.ConnectionPool.safeClose(ConnectionPool.java:177) at org.jboss.ejb.client.remoting.ConnectionPool.release(ConnectionPool.java:104) at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.close(ConnectionPool.java:198) at org.jboss.ejb.client.remoting.RemotingConnectionManager.safeClose(RemotingConnectionManager.java:65) at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector$ContextCloseListener.contextClosed(ConfigBasedEJBClientContextSelector.java:220) at org.jboss.ejb.client.EJBClientContext.close(EJBClientContext.java:1305) at org.jboss.ejb.client.EJBClientContext.finalize(EJBClientContext.java:1316) at java.lang.System$2.invokeFinalize(System.java:1270) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:98) at java.lang.ref.Finalizer.access$100(Finalizer.java:34) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:210)

    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