Yes, I'm using standalone.xml.
To reproduce the odd behaviour, it's very simple (in windows, at least):
- Download WF 10.0.0.Final
- Execute "stanalone.bat"
Use netstat, and filter for PID, to see the unexpected connections.
If you dig further, like I did, and enable TRACE for XNIO, nothing related
with these connections shows up. Capturing the traffic (I use WinCap for
localhost captures in windows), you'll see the the pattern I referred
On Sun, Apr 10, 2016 at 9:11 PM, Ken Wills <ken(a)zaptillion.net> wrote:
On Sun, Apr 10, 2016 at 12:50 PM, Luís M. Costa <luis.m.costa(a)gmail.com>
> I'm using standalone.
Quick note, when I looked at the forum on Friday, it wasn't showing me any
responses to your original post, so sorry for the duplicate questions. I
see that there are a few responses prior.
What configuration are you using? standalone.xml? I've had a quick look on
linux and I don't see the same behavior, but perhaps I'm not using the same
> I've observed the problem both in WF 8.2.1.Final and WF 10.0.0.Final. The
> type of connection, and communication pattern, is the same. This is
> observable in Windows (I haven't tried any linux flavor) running as
> Administrator or Windows Service. I've been using JDK 8u20, but it is also
> observable with the latest JDK release.
> I find this connections very intriguing, and I'm hopping to understand
> what sub-system may be responsible, in order to deal with the problem I
> described in the forum.
> On Fri, Apr 8, 2016 at 10:49 PM, Ken Wills <ken(a)zaptillion.net> wrote:
>> On Thu, Apr 7, 2016 at 4:03 PM, Luís M. Costa <luis.m.costa(a)gmail.com>
>>> Wildfly 10 final (just downloaded / no applications deployed / port
>>> Windows 7 64bits
>>> Java 8u20
>>> Can someone clarify why is this happening? Or provide some
>>> troubleshooting tips?
>> Are you starting a domain, or standalone?
>>> I've reported a problem related with this in the user's forum, but I
>>> still don't have a answer.
>>> Link: https://developer.jboss.org/message/953900
>> The forum post says you were using WF8.2.1-Final, is this happening with
>> both 10 and 8?
>> The first thing I'd try is make sure you're running the process as
>> administrator and see if the same thing occurs, perhaps it's a permissions