Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-392

EJB connection close does not close the connection cleanly instead logs a warning 'Failed to close ssl engine'.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 5.0.24.Final
    • None
    • Hide

      Close the EJB connection from client side with EJBClientContext.getCurrent().close() call
      and exit the JVM.

      Show
      Close the EJB connection from client side with EJBClientContext.getCurrent().close() call and exit the JVM.

      With the below code we try to notify the server for EJB connection close before client app closing.

      try {
      EJBClientContext.getCurrent().close();
      initialContext.close(); //org.wildfly.naming.client.WildFlyInitialContext        
} catch (NamingException e) {
      throw new ServiceLocatorException("could not close context", e);
    }

      But then on the server side we receive a warning as below when the client exits:

      2022-07-13 12:27:13,742 WARN  [org.xnio] (default I/O-5) XNIO000307: Failed to close ssl engine when handling exception java.io.IOException: An existing connection was forcibly closed by the remote host: java.io.IOException: An existing connection was forcibly closed by the remote host
    at java.base/sun.nio.ch.SocketDispatcher.write0(Native Method)
    at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
    at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113)
    at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:58)
    at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50)
    at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:462)
    at org.jboss.xnio.nio@3.8.7.Final//org.xnio.nio.NioSocketConduit.write(NioSocketConduit.java:153)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslConduitEngine.doFlush(JsseSslConduitEngine.java:863)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslConduitEngine.handleWrapResult(JsseSslConduitEngine.java:410)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslConduitEngine.wrapCloseMessage(JsseSslConduitEngine.java:835)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslConduitEngine.closeOutbound(JsseSslConduitEngine.java:916)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslConduitEngine.close(JsseSslConduitEngine.java:955)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ssl.JsseSslStreamConnection.closeAction(JsseSslStreamConnection.java:126)
    at org.jboss.xnio@3.8.7.Final//org.xnio.Connection.close(Connection.java:132)
    at org.jboss.xnio@3.8.7.Final//org.xnio.IoUtils.safeClose(IoUtils.java:152)
    at org.jboss.remoting@5.0.24.Final//org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:117)
    at org.jboss.remoting@5.0.24.Final//org.jboss.remoting3.remote.RemoteConnection.handleException(RemoteConnection.java:104)
    at org.jboss.remoting@5.0.24.Final//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:540)
    at org.jboss.remoting@5.0.24.Final//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:51)
    at org.jboss.xnio@3.8.7.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    at org.jboss.xnio@3.8.7.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
    at org.jboss.xnio.nio@3.8.7.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
    at org.jboss.xnio.nio@3.8.7.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

      As the client notified the server to close the channel, the server should close the channel gracefully with out any warnings on client exit.

            Unassigned Unassigned
            yuva0425 Yuva Kishore Bollina (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: