EAP 7 occassionally logs 'Broken Pipe' WARN message when CLI connection terminates

Solution Unverified - Updated -

Issue

  • Sometimes, after accessing JBoss using the native interface (SSL) via JBoss CLI, the following warning can be seen in the domain controller host-controller.log occasionally when the connection closes:
09:30,006 WARN  [org.xnio] (management I/O-2) XNIO000307: Failed to close ssl engine when handling exception java.io.IOException: Broken pipe: java.io.IOException: Broken pipe
 at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method)
 at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
 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:466)
 at org.jboss.xnio.nio@3.7.12.Final-redhat-00001//org.xnio.nio.NioSocketConduit.write(NioSocketConduit.java:153)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.doFlush(JsseSslConduitEngine.java:865)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.handleWrapResult(JsseSslConduitEngine.java:411)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.wrapCloseMessage(JsseSslConduitEngine.java:837)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.closeOutbound(JsseSslConduitEngine.java:911)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.handleHandshake(JsseSslConduitEngine.java:475)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslConduitEngine.unwrap(JsseSslConduitEngine.java:635) at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ssl.JsseSslStreamSourceConduit.read(JsseSslStreamSourceConduit.java:126)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:123)
 at org.jboss.remoting@5.0.20.Final-redhat-00001//org.jboss.remoting3.remote.MessageReader.getMessage(MessageReader.java:139)
 at org.jboss.remoting@5.0.20.Final-redhat-00001//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:83)
 at org.jboss.remoting@5.0.20.Final-redhat-00001//org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:49)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
 at org.jboss.xnio@3.7.12.Final-redhat-00001//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
 at org.jboss.xnio.nio@3.7.12.Final-redhat-00001//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
 at org.jboss.xnio.nio@3.7.12.Final-redhat-00001//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content