Uploaded image for project: 'XNIO'
  1. XNIO
  2. XNIO-215

Infinite Loops after connection establishment failure for HttpUpgrade with SSL

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.2.0.Final
    • 3.1.0.Final
    • None
    • None

      If establishing the SSL connection fails the thread establishing the connection is going into an infinite loop.

      For the looping thread the following stack is regularly encountered, essentially an error condition is detected but nothing happens to actually stop the loop attempting to make use of the connection: -

      "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)
      

            darran.lofthouse@redhat.com Darran Lofthouse
            darran.lofthouse@redhat.com Darran Lofthouse
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: