11:18 a.m.
Hi all,
One of the changes from EAP 5 to 6 is that the -b option no longer "just works"
and requires the admin to change the configuration to use <loopback-address/>
instead of <inet-address/>.
Some of my customers were surprised by the change. They enjoyed the ease of use that -b
gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b
does just work (at least on the RHEL vms I tested). Does this mean that users can expect
to see -b back in play (ie w/o need for config changes) for EAP 7?
Thanks.
Phil Festoso
Sr. Technical Account Manager, Global Support Services
Red Hat, Inc.
T: 312.612.0035
E: philfest(a)redhat.com
11:27 a.m.
Huh?
-b does work, and the default is now loopback. The only thing that is really different is
that we have a -b for the application ports and a -bmanagement for management ports.
On Jan 23, 2015, at 11:18 AM, Phil Festoso
<pfestoso(a)redhat.com> wrote:
Hi all,
One of the changes from EAP 5 to 6 is that the -b option no longer "just works"
and requires the admin to change the configuration to use <loopback-address/>
instead of <inet-address/>.
Some of my customers were surprised by the change. They enjoyed the ease of use that -b
gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b
does just work (at least on the RHEL vms I tested). Does this mean that users can expect
to see -b back in play (ie w/o need for config changes) for EAP 7?
Thanks.
Phil Festoso
Sr. Technical Account Manager, Global Support Services
Red Hat, Inc.
T: 312.612.0035
E: philfest(a)redhat.com
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11:28 a.m.
I mean its been like that since AS 7.0.0.
On Jan 23, 2015, at 11:27 AM, Jason Greene
<jason.greene(a)redhat.com> wrote:
Huh?
-b does work, and the default is now loopback. The only thing that is really different is
that we have a -b for the application ports and a -bmanagement for management ports.
> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> Hi all,
>
> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>
>
> Some of my customers were surprised by the change. They enjoyed the ease of use that
-b gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b
does just work (at least on the RHEL vms I tested). Does this mean that users can expect
to see -b back in play (ie w/o need for config changes) for EAP 7?
>
> Thanks.
>
> Phil Festoso
> Sr. Technical Account Manager, Global Support Services
> Red Hat, Inc.
> T: 312.612.0035
> E: philfest(a)redhat.com
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11:28 a.m.
Maybe this is a problem on some specific OS / JVM combination?
As for most of the cases we know of it works.
On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com>
wrote:
Huh?
-b does work, and the default is now loopback. The only thing that is
really different is that we have a -b for the application ports and a
-bmanagement for management ports.
> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> Hi all,
>
> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>
>
> Some of my customers were surprised by the change. They enjoyed the ease
of use that -b gave them and are hoping to see that feature brought back. I
noticed that in WF 8.2 -b does just work (at least on the RHEL vms I
tested). Does this mean that users can expect to see -b back in play (ie
w/o need for config changes) for EAP 7?
>
> Thanks.
>
> Phil Festoso
> Sr. Technical Account Manager, Global Support Services
> Red Hat, Inc.
> T: 312.612.0035
> E: philfest(a)redhat.com
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
11:32 a.m.
Well our configuration for all releases of AS7, EAP and WildFly specifies:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t think that is
even possible.
On Jan 23, 2015, at 11:28 AM, Tomaž Cerar
<tomaz.cerar(a)gmail.com> wrote:
Maybe this is a problem on some specific OS / JVM combination?
As for most of the cases we know of it works.
On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
Huh?
-b does work, and the default is now loopback. The only thing that is really different is
that we have a -b for the application ports and a -bmanagement for management ports.
> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> Hi all,
>
> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>
>
> Some of my customers were surprised by the change. They enjoyed the ease of use that
-b gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b
does just work (at least on the RHEL vms I tested). Does this mean that users can expect
to see -b back in play (ie w/o need for config changes) for EAP 7?
>
> Thanks.
>
> Phil Festoso
> Sr. Technical Account Manager, Global Support Services
> Red Hat, Inc.
> T: 312.612.0035
> E: philfest(a)redhat.com
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11:44 a.m.
Just mentioned it as in mac osx when you start standalone-ha.xml with -b
0.0.0.0
jgroups complains about not being able to bind and you get some ugly
warning / error.
On Fri, Jan 23, 2015 at 6:32 PM, Jason Greene <jason.greene(a)redhat.com>
wrote:
Well our configuration for all releases of AS7, EAP and WildFly
specifies:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t
think that is even possible.
> On Jan 23, 2015, at 11:28 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
>
> Maybe this is a problem on some specific OS / JVM combination?
>
> As for most of the cases we know of it works.
>
>
> On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com>
wrote:
> Huh?
>
> -b does work, and the default is now loopback. The only thing that is
really different is that we have a -b for the application ports and a
-bmanagement for management ports.
>
>
> > On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com>
wrote:
> >
> > Hi all,
> >
> > One of the changes from EAP 5 to 6 is that the -b option no longer
"just works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
> >
> >
> > Some of my customers were surprised by the change. They enjoyed the
ease of use that -b gave them and are hoping to see that feature brought
back. I noticed that in WF 8.2 -b does just work (at least on the RHEL vms
I tested). Does this mean that users can expect to see -b back in play (ie
w/o need for config changes) for EAP 7?
> >
> > Thanks.
> >
> > Phil Festoso
> > Sr. Technical Account Manager, Global Support Services
> > Red Hat, Inc.
> > T: 312.612.0035
> > E: philfest(a)redhat.com
> >
> > _______________________________________________
> > wildfly-dev mailing list
> > wildfly-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11:49 a.m.
More context is needed. Apologies.
In EAP 6, I'm restricted to the known loopback address. So, if I try -b 127.0.1.1,
the service won't start without adding an alias to the lo interface. In WF 8.2
I've had success using anything under 127.0.*.* without the need for an alias. This is
true for RHEL 6.5 and 7 with oracle jdk 1.7_71, and does not work on my win 7 pc at home,
so there might be something to the notion that this behavior is dependent on JDK/OS
pairings.
Hope that clarifies things. Thanks for the responses.
----- Original Message -----
From: "Jason Greene" <jason.greene(a)redhat.com>
To: "Tomaž Cerar" <tomaz.cerar(a)gmail.com>
Cc: "Phil Festoso" <pfestoso(a)redhat.com>, wildfly-dev(a)lists.jboss.org
Sent: Friday, January 23, 2015 11:32:42 AM
Subject: Re: [wildfly-dev] WF 8 vs EAP 6 and use of -b
Well our configuration for all releases of AS7, EAP and WildFly specifies:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t think that is
even possible.
On Jan 23, 2015, at 11:28 AM, Tomaž Cerar
<tomaz.cerar(a)gmail.com> wrote:
Maybe this is a problem on some specific OS / JVM combination?
As for most of the cases we know of it works.
On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
Huh?
-b does work, and the default is now loopback. The only thing that is really different is
that we have a -b for the application ports and a -bmanagement for management ports.
> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> Hi all,
>
> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>
>
> Some of my customers were surprised by the change. They enjoyed the ease of use that
-b gave them and are hoping to see that feature brought back. I noticed that in WF 8.2 -b
does just work (at least on the RHEL vms I tested). Does this mean that users can expect
to see -b back in play (ie w/o need for config changes) for EAP 7?
>
> Thanks.
>
> Phil Festoso
> Sr. Technical Account Manager, Global Support Services
> Red Hat, Inc.
> T: 312.612.0035
> E: philfest(a)redhat.com
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
11:53 a.m.
Ah yes, originally we verified there was an interface available on the OS that was
assigned that IP, but removed the validation code to make it more flexible for OSs which
support dynamic loopback IPs (Linux). Windows does not support that concept which is why
you saw it fail.
On Jan 23, 2015, at 11:49 AM, Phil Festoso
<pfestoso(a)redhat.com> wrote:
More context is needed. Apologies.
In EAP 6, I'm restricted to the known loopback address. So, if I try -b 127.0.1.1,
the service won't start without adding an alias to the lo interface. In WF 8.2
I've had success using anything under 127.0.*.* without the need for an alias. This is
true for RHEL 6.5 and 7 with oracle jdk 1.7_71, and does not work on my win 7 pc at home,
so there might be something to the notion that this behavior is dependent on JDK/OS
pairings.
Hope that clarifies things. Thanks for the responses.
----- Original Message -----
From: "Jason Greene" <jason.greene(a)redhat.com>
To: "Tomaž Cerar" <tomaz.cerar(a)gmail.com>
Cc: "Phil Festoso" <pfestoso(a)redhat.com>, wildfly-dev(a)lists.jboss.org
Sent: Friday, January 23, 2015 11:32:42 AM
Subject: Re: [wildfly-dev] WF 8 vs EAP 6 and use of -b
Well our configuration for all releases of AS7, EAP and WildFly specifies:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t think that is
even possible.
> On Jan 23, 2015, at 11:28 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
>
> Maybe this is a problem on some specific OS / JVM combination?
>
> As for most of the cases we know of it works.
>
>
> On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
> Huh?
>
> -b does work, and the default is now loopback. The only thing that is really
different is that we have a -b for the application ports and a -bmanagement for management
ports.
>
>
>> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>>
>> Hi all,
>>
>> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>>
>>
>> Some of my customers were surprised by the change. They enjoyed the ease of use
that -b gave them and are hoping to see that feature brought back. I noticed that in WF
8.2 -b does just work (at least on the RHEL vms I tested). Does this mean that users can
expect to see -b back in play (ie w/o need for config changes) for EAP 7?
>>
>> Thanks.
>>
>> Phil Festoso
>> Sr. Technical Account Manager, Global Support Services
>> Red Hat, Inc.
>> T: 312.612.0035
>> E: philfest(a)redhat.com
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
12:38 p.m.
Thanks for that. Will pass along to the cust.
----- Original Message -----
From: "Jason Greene" <jason.greene(a)redhat.com>
To: "Phil Festoso" <pfestoso(a)redhat.com>
Cc: wildfly-dev(a)lists.jboss.org
Sent: Friday, January 23, 2015 11:53:58 AM
Subject: Re: [wildfly-dev] WF 8 vs EAP 6 and use of -b
Ah yes, originally we verified there was an interface available on the OS that was
assigned that IP, but removed the validation code to make it more flexible for OSs which
support dynamic loopback IPs (Linux). Windows does not support that concept which is why
you saw it fail.
On Jan 23, 2015, at 11:49 AM, Phil Festoso
<pfestoso(a)redhat.com> wrote:
More context is needed. Apologies.
In EAP 6, I'm restricted to the known loopback address. So, if I try -b 127.0.1.1,
the service won't start without adding an alias to the lo interface. In WF 8.2
I've had success using anything under 127.0.*.* without the need for an alias. This is
true for RHEL 6.5 and 7 with oracle jdk 1.7_71, and does not work on my win 7 pc at home,
so there might be something to the notion that this behavior is dependent on JDK/OS
pairings.
Hope that clarifies things. Thanks for the responses.
----- Original Message -----
From: "Jason Greene" <jason.greene(a)redhat.com>
To: "Tomaž Cerar" <tomaz.cerar(a)gmail.com>
Cc: "Phil Festoso" <pfestoso(a)redhat.com>, wildfly-dev(a)lists.jboss.org
Sent: Friday, January 23, 2015 11:32:42 AM
Subject: Re: [wildfly-dev] WF 8 vs EAP 6 and use of -b
Well our configuration for all releases of AS7, EAP and WildFly specifies:
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t think that is
even possible.
> On Jan 23, 2015, at 11:28 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
>
> Maybe this is a problem on some specific OS / JVM combination?
>
> As for most of the cases we know of it works.
>
>
> On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
> Huh?
>
> -b does work, and the default is now loopback. The only thing that is really
different is that we have a -b for the application ports and a -bmanagement for management
ports.
>
>
>> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>>
>> Hi all,
>>
>> One of the changes from EAP 5 to 6 is that the -b option no longer "just
works" and requires the admin to change the configuration to use
<loopback-address/> instead of <inet-address/>.
>>
>>
>> Some of my customers were surprised by the change. They enjoyed the ease of use
that -b gave them and are hoping to see that feature brought back. I noticed that in WF
8.2 -b does just work (at least on the RHEL vms I tested). Does this mean that users can
expect to see -b back in play (ie w/o need for config changes) for EAP 7?
>>
>> Thanks.
>>
>> Phil Festoso
>> Sr. Technical Account Manager, Global Support Services
>> Red Hat, Inc.
>> T: 312.612.0035
>> E: philfest(a)redhat.com
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
2:31 p.m.
https://issues.jboss.org/browse/WFLY-248
https://github.com/wildfly/wildfly/pull/4706
Rostislav
----- Original Message -----
Ah yes, originally we verified there was an interface available on
the OS
that was assigned that IP, but removed the validation code to make it more
flexible for OSs which support dynamic loopback IPs (Linux). Windows does
not support that concept which is why you saw it fail.
> On Jan 23, 2015, at 11:49 AM, Phil Festoso <pfestoso(a)redhat.com> wrote:
>
> More context is needed. Apologies.
>
> In EAP 6, I'm restricted to the known loopback address. So, if I try -b
> 127.0.1.1, the service won't start without adding an alias to the lo
> interface. In WF 8.2 I've had success using anything under 127.0.*.*
> without the need for an alias. This is true for RHEL 6.5 and 7 with oracle
> jdk 1.7_71, and does not work on my win 7 pc at home, so there might be
> something to the notion that this behavior is dependent on JDK/OS
> pairings.
>
> Hope that clarifies things. Thanks for the responses.
>
> ----- Original Message -----
> From: "Jason Greene" <jason.greene(a)redhat.com>
> To: "Tomaž Cerar" <tomaz.cerar(a)gmail.com>
> Cc: "Phil Festoso" <pfestoso(a)redhat.com>,
wildfly-dev(a)lists.jboss.org
> Sent: Friday, January 23, 2015 11:32:42 AM
> Subject: Re: [wildfly-dev] WF 8 vs EAP 6 and use of -b
>
> Well our configuration for all releases of AS7, EAP and WildFly specifies:
>
> <interface name="public">
> <inet-address value="${jboss.bind.address:127.0.0.1}"/>
> </interface>
>
> So unless 127.0.0.1 was somehow bound to a non-loopback interface I don’t
> think that is even possible.
>
>> On Jan 23, 2015, at 11:28 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
>>
>> Maybe this is a problem on some specific OS / JVM combination?
>>
>> As for most of the cases we know of it works.
>>
>>
>> On Fri, Jan 23, 2015 at 6:27 PM, Jason Greene <jason.greene(a)redhat.com>
>> wrote:
>> Huh?
>>
>> -b does work, and the default is now loopback. The only thing that is
>> really different is that we have a -b for the application ports and a
>> -bmanagement for management ports.
>>
>>
>>> On Jan 23, 2015, at 11:18 AM, Phil Festoso <pfestoso(a)redhat.com>
wrote:
>>>
>>> Hi all,
>>>
>>> One of the changes from EAP 5 to 6 is that the -b option no longer
"just
>>> works" and requires the admin to change the configuration to use
>>> <loopback-address/> instead of <inet-address/>.
>>>
>>>
>>> Some of my customers were surprised by the change. They enjoyed the ease
>>> of use that -b gave them and are hoping to see that feature brought
>>> back. I noticed that in WF 8.2 -b does just work (at least on the RHEL
>>> vms I tested). Does this mean that users can expect to see -b back in
>>> play (ie w/o need for config changes) for EAP 7?
>>>
>>> Thanks.
>>>
>>> Phil Festoso
>>> Sr. Technical Account Manager, Global Support Services
>>> Red Hat, Inc.
>>> T: 312.612.0035
>>> E: philfest(a)redhat.com
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3590
days inactive
3590
days old
9 comments
4 participants
participants (4)
-
Jason Greene -
Phil Festoso -
Rostislav Svoboda -
Tomaž Cerar