[
https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin....
]
Chris Stillwell updated WFLY-3290:
----------------------------------
Attachment: helloworld-test.zip
The helloworld-test.zip file contains the source for a simple Stateless session bean, the
deployment ear, the standalone.conf, and standalone-ha.xml files I used to test this
issue.
standalone01-ha.xml adds a remote-outbound-connection named helloworld-connection. The
cluster name remains "ejb".
standalone02-ha.xml is the same as standalone01-ha.xml, but changes the cluster name to
ejb-helloworld.
standalone.conf is modified to set the helloworldServer1 variable used in the helloworld
outbound-socket-binding in the standalone01 & 02 configs and to override the variables
jboss.bind.address.management, jboss.bind.address, and jboss.default.multicast.address.
When the ear is deployed using the standalone01-ha.xml configuration the cluster will be
formed. However, when using the standalone02-ha.xml configuration the cluster will not be
formed.
Cannot use a cluster name other than "ejb"
------------------------------------------
Key: WFLY-3290
URL:
https://issues.jboss.org/browse/WFLY-3290
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.Final
Reporter: Chris Stillwell
Assignee: Paul Ferraro
Priority: Critical
Attachments: helloworld-test.zip
When deploying a clustered session bean the cluster will form only if the cluster name is
"ejb". If the standalone-ha.xml is modified to use a different cluster name
then the cluster will not form.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira