Is this standalone.xml or standalone-full.xml or something else?
as you can see in your ports.txt there are only two listening ports
TCP 127.0.0.1:8080 MachineName:0 LISTENING 6612 TCP 127.0.0.1:9990 MachineName:0 LISTENING 6612
all the others are already established connections.
It is hard to say what exactly they are beyond that they are comming from local host.
that could be anything that connects to wildfly.
either web browser, proxy server, or some other software connecting to it,
That is all i can tell you based on data you posted.
Thanks for taking the time to reply. I'm guessing you don't see this behaviour on your environments! To answer your questions:
This is for just standalone.xml.
And the netstat was done just after WildFly started up, before I tried to visit any web pages or otherwise access WildFly's services - so I don't think there can be anything external connecting to WildFly.
Also, the process id of all those ports is the same (i.e. the WildFly java process), which is why I thought that WildFly by itself was responsible for those ports.
I found some time to attach a debugger to the WildFly process, and added a breakpoint to the java.net.Socket constructors. I found that the sockets are being constructed by Java NIO, as part of the creation of an XNIO worker thread - this explains why there are so many - it would appear you get a pair of sockets for each thread. This would seem to agree with a comment in the WorkerAdd class saying that each worker thread needs two file descriptors.
I don't fully understand how NIO works, but I feel satisfied that these port pairs are simply an artifact of how Java NIO is implemented.
FYI, the route to the Socket construction is: