[
https://issues.jboss.org/browse/WFLY-5358?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-5358:
------------------------------------
JGroups properties are subject to deprecations across releases. This is normal.
This is documented in the description of the associated attribute of the runtime channel
(available from the management interface), as well as in the exception message itself.
The exception messages are fairly self-explanatory.
JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout
should be used instead
------------------------------------------------------------------------------------------
Key: WFLY-5358
URL:
https://issues.jboss.org/browse/WFLY-5358
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR1
Reporter: Carlton Zachary
Assignee: Paul Ferraro
I am getting the following in the server.log when using the HA profile and with a Cluster
application deployed.
WARN [org.jgroups.stack.Configurator] (MSC service thread 1-2) JGRP000014:
Discovery.timeout has been deprecated: GMS.join_timeout should be used instead
WARN [org.jgroups.stack.Configurator] (MSC service thread 1-2) JGRP000014:
Discovery.num_initial_members has been deprecated: will be ignored
JGroups configuration:
<stacks default="tcp">
<stack name="tcp">
<transport type="TCP"
socket-binding="jgroups-tcp"/>
<protocol type="TCPPING">
<property name="initial_hosts">
${jboss.cluster.tcp.initial_hosts}
</property>
<property name="num_initial_members">
2
</property>
<property name="port_range">
0
</property>
<property name="timeout">
2000
</property>
</protocol>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)