[
https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz commented on WFLY-3290:
-------------------------------------------
Proposal would be to add a new "cluster" element to the EJB3 subsystem's
remote element, so that that name will be used in topology updates returned to the client
from the cluster, along with the client mappings. So for example, to change the name of
the cluster as in the example above:
{noformat}
<subsystem xmlns="urn:jboss:domain:ejb3:3.0">
...
<remote connector-ref="http-remoting-connector"
thread-pool-name="default" cluster="ejb-helloworld"/>
...
</subsystem>
<subsystem xmlns="urn:jboss:domain:infinispan:3.0">
...
<cache-container name="ejb" aliases="sfsb"
default-cache="dist"
module="org.wildfly.clustering.ejb.infinispan">
<transport lock-timeout="60000"/>
<distributed-cache name="dist" mode="ASYNC"
l1-lifespan="0" owners="2">
<transaction mode="BATCH"/>
<file-store/>
</distributed-cache>
</cache-container>
...
<cache-container name="ejb-helloworld" default-cache="dist"
module="org.wildfly.clustering.ejb.infinispan">
<transport lock-timeout="60000"/>
<distributed-cache name="dist" mode="ASYNC"
l1-lifespan="0" owners="2">
<transaction mode="BATCH"/>
<file-store/>
</distributed-cache>
</cache-container>
...
</subsystem>
{noformat}
Cannot use a cluster name other than "ejb"
------------------------------------------
Key: WFLY-3290
URL:
https://issues.jboss.org/browse/WFLY-3290
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.0.0.Final
Reporter: Chris Stillwell
Assignee: Richard Achmatowicz
Priority: Critical
Fix For: 9.0.0.CR1
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 was sent by Atlassian JIRA
(v6.3.15#6346)