0 Replies Latest reply on Oct 5, 2018 12:47 PM by Oluwasegun Diyan

    Ephemeral Ports Exhausted

    Oluwasegun Diyan Newbie

      Hi,

       

      I have a funny scenario where my wildfly instance (Wildfly 9.0.2) on my Windows server (Windows 2012 R2-Standard) appears to be exhausting the dynamic port range of the euphemeral ports.

      From netstat, these ports appear to be used by "ESTABLISHED loopback connections".

       

      After much digging I discovered that the count of loopback connections appear to be affected by the number or io-threads specified in the io-subsystem of my Wildfly standalone XML.

       

      IO-THREADSTask Max ThreadNo of Loopback Connections
      1001000454
      501000305
      101000225

       

      Why does Wildfly create so many loopback connections? How can I derive the optimal number of io-threads required for our apps to run while not exhausting the dynamic port range?

       

      Thanks in advance!

       

      Further environment information:

      Server: Windows Server 2012 R2 Standard

      Processor: Intel(R) Xeon(R) CPU E5-2670 v3 @2.30GHz 2.30GHz (6 processors)

      RAM: 64GB

      System Type: 64-bit Operating System