2 Replies Latest reply on May 24, 2018 5:40 PM by Carl Walker

    WF 10 Client Remoting Connections Closed

    Carl Walker Newbie

      Hi,

      I've been running with WF 10 for about a year and started seeing these errors pop up.  The architecture is a desktop client using EJB HTTP Remoting.

       

      I don't have a lot of info on this besides the following stack trace.  The users experiencing this are actively using the app and that the failure comes when they make a Remote EJB call.  At the point of the error, they will have made several Remote EJB calls.

       

      This particular server has an above average of remote clients, so I was wondering if a pool might be set too low.

       

      Any help is appreciated,

      Carl

       

      Caused by: java.io.IOException: Channel Channel ID c40a3295 (outbound) of Remoting connection 5d4c6b78 to /xxx.xxx.xxxx.xxx:8080 of endpoint "config-based-ejb-client-endpoint" <1f5464d> 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:444)

      at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:237)

      at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:420)

      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(Unknown Source)

      at java.lang.ref.Finalizer.runFinalizer(Unknown Source)

      at java.lang.ref.Finalizer.access$100(Unknown Source)

      at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)