[jboss-jira] [JBoss JIRA] (WFLY-2490) Connecting using https-remoting times out and leaves thread within CLI spinning at 100%

Monday, 11 November 2013



    [
https://issues.jboss.org/browse/WFLY-2490?page=com.atlassian.jira.plugin....
] 

Darran Lofthouse edited comment on WFLY-2490 at 11/11/13 1:23 PM:
------------------------------------------------------------------

I believe it is the "Remoting "cli-client" I/O-1" thread that is in
the loop, here are a couple of stacks captured whilst at 100% CPU for this thread: -

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at java.lang.Throwable.fillInStackTrace(Native Method)
	at java.lang.Throwable.fillInStackTrace(Throwable.java:782)
	- locked <0x00000000d88a88c8> (a java.io.EOFException)
	at java.lang.Throwable.<init>(Throwable.java:265)
	at java.lang.Exception.<init>(Exception.java:66)
	at java.io.IOException.<init>(IOException.java:58)
	at java.io.EOFException.<init>(EOFException.java:63)
	at org.xnio._private.Messages_$logger.connectionClosedEarly(Messages_$logger.java:859)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:282)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:265)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at
org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)
{noformat}

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225)
	at sun.nio.ch.IOUtil.read(IOUtil.java:198)
	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359)
	- locked <0x00000000869920a0> (a java.lang.Object)
	at org.xnio.nio.NioSocketConduit.read(NioSocketConduit.java:270)
	at
org.xnio.conduits.AbstractStreamSourceConduit.read(AbstractStreamSourceConduit.java:51)
	at org.xnio.ssl.JsseSslStreamSourceConduit.read(JsseSslStreamSourceConduit.java:74)
	at
org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:276)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:265)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at
org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)
{noformat}

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
	at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:228)
	at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:81)
	at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
	- locked <0x0000000086b42658> (a sun.nio.ch.Util$2)
	- locked <0x0000000086b42648> (a java.util.Collections$UnmodifiableSet)
	- locked <0x0000000086991a80> (a sun.nio.ch.EPollSelectorImpl)
	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:102)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:494)
{noformat}

Note - Despite the looping additional connections are not be created to the server: -

{noformat}
[darranl@localhost bin]$ netstat -anop | grep 9993
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:9993          0.0.0.0:*               LISTEN      32698/java
          off (0.00/0/0)
tcp6       0      0 127.0.0.1:48415         127.0.0.1:9993          CLOSE_WAIT  337/java  
          off (0.00/0/0)
{noformat}
                
      was (Author: dlofthouse):
    I believe it is the "Remoting "cli-client" I/O-1" thread that is
in the loop, here are a couple of stacks captured whilst at 100% CPU for this thread: -

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at java.lang.Throwable.fillInStackTrace(Native Method)
	at java.lang.Throwable.fillInStackTrace(Throwable.java:782)
	- locked <0x00000000d88a88c8> (a java.io.EOFException)
	at java.lang.Throwable.<init>(Throwable.java:265)
	at java.lang.Exception.<init>(Exception.java:66)
	at java.io.IOException.<init>(IOException.java:58)
	at java.io.EOFException.<init>(EOFException.java:63)
	at org.xnio._private.Messages_$logger.connectionClosedEarly(Messages_$logger.java:859)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:282)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:265)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at
org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)
{noformat}

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
	at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
	at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225)
	at sun.nio.ch.IOUtil.read(IOUtil.java:198)
	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359)
	- locked <0x00000000869920a0> (a java.lang.Object)
	at org.xnio.nio.NioSocketConduit.read(NioSocketConduit.java:270)
	at
org.xnio.conduits.AbstractStreamSourceConduit.read(AbstractStreamSourceConduit.java:51)
	at org.xnio.ssl.JsseSslStreamSourceConduit.read(JsseSslStreamSourceConduit.java:74)
	at
org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:276)
	at
org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:265)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at
org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:528)
{noformat}

{noformat}
"Remoting "cli-client" I/O-1" daemon prio=10 tid=0x00007fe48857f000
nid=0x173 runnable [0x00007fe46e172000]
   java.lang.Thread.State: RUNNABLE
	at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
	at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:228)
	at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:81)
	at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
	- locked <0x0000000086b42658> (a sun.nio.ch.Util$2)
	- locked <0x0000000086b42648> (a java.util.Collections$UnmodifiableSet)
	- locked <0x0000000086991a80> (a sun.nio.ch.EPollSelectorImpl)
	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:102)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:494)
{noformat}
                  
...
 Connecting using https-remoting times out and leaves thread within
CLI spinning at 100%
 ---------------------------------------------------------------------------------------

                 Key: WFLY-2490
                 URL: https://issues.jboss.org/browse/WFLY-2490
             Project: WildFly
          Issue Type: Sub-task
      Security Level: Public(Everyone can see) 
          Components: CLI, Remoting
            Reporter: Darran Lofthouse
            Assignee: Darran Lofthouse

 HTTP Upgrade is not fully working when SSL is enabled, other tasks will address that but
this issue is about the CLI connecting to a server where HTTP Upgrade is not possible - a
thread within the CLI is left running at 100% even after connecting has timed out.
 {noformat}
 [disconnected /] connect https-remoting://localhost:9993
 The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144:
Could not connect to https-remoting://localhost:9993. The connection timed out:
JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed
out
 {noformat}
 Connecting to the HTTP port where HTTP Upgrade is not available also results in a time
out connecting rather than an early failure but does not result in the thread spinning at
100%
 {noformat}
 [disconnected /] connect http-remoting://localhost:9990
 The controller is not available at localhost:9990: java.net.ConnectException: JBAS012144:
Could not connect to http-remoting://localhost:9990. The connection timed out: JBAS012144:
Could not connect to http-remoting://localhost:9990. The connection timed out
 {noformat} 
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[jboss-jira] [JBoss JIRA] (WFLY-2490) Connecting using https-remoting times out and leaves thread within CLI spinning at 100%