Hey,
this is not proper mailing list for this kind of questions anymore given
that wildfly does not contain web subsystem anymore.
in any case, my memory around this is fading so take this with grain of
salt :-)
if instance-id is not set if defaults to jboss.node.name in case you are
proxying directly to web, but in case of mod-cluster integration mod
cluster generates its own id that does not folow same convetion unless
instance-id is defined.
I don't see any big reason why not change default, but it should in any
case get bugzilla entry so it could be considered for fix in EAP.
I will make sure undertow's instance-id will have proper defaults but for
EAP go trough "official" channels.
--
tomaz
On Wed, Jan 22, 2014 at 2:03 AM, Claudio Miranda <claudio(a)claudius.com.br>wrote:
Hi, for every server that wants to work in a cluster with
mod_cluster,
they need to set instance-id="${jboss.node.name}" in the web subsystem
[1].
Also for every jboss server I configure, I set this property.
I suggest to let this as default in domain.xml and standalone.xml,
what do you think ?
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Appli...
--
Claudio Miranda
claudio(a)claudius.com.br
http://www.claudius.com.br
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev