[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Preeta Kuruvilla edited comment on WFLY-6781 at 6/29/16 10:18 AM: ------------------------------------------------------------------ The cluster that we have is a domain managed cluster where we have domain.xml and host.xml configured on Node1 and only host.xml configured on Node2. The jgroups is a subsystem in the domain.xml for the profile "ha". Regarding our application, we have 2 components - RC.war and SL.war. The JMS is configured on SL. Only component RC is clustered. SL is not clustered. In domain.xml we have:- <server-groups> <server-group name="main-server-group" profile="ha"> <socket-binding-group ref="ha-sockets"/> <deployments> <deployment name="RC.war" runtime-name="RC.war"/> </deployments> </server-group> <server-group name="other-server-group" profile="ha"> <socket-binding-group ref="standard-sockets"/> <paths> <path name="jboss.server.log.dir.SL" path="jboss.server.log.dir" /> </paths> <deployments> <deployment name="SL.war" runtime-name="SL.war"/> </deployments> </server-group> </server-groups> *********************** In host.xml we have:- Node 1 has - 2 server instances- RC and SL. <servers> <server name="server-host1-RC" group="main-server-group" auto-start="true"> <jvm name="default"> ............ </jvm-options> </jvm> <socket-bindings socket-binding-group="ha-sockets" port-offset="0"/> </server> <server name="server-host1-SL" group="other-server-group" auto-start="true"> <jvm name="default"> ........ </jvm-options> </jvm> <socket-bindings socket-binding-group="standard-sockets" port-offset="0"/> </server> </servers> Node 2 : has only one server instance and that has RC <servers> <server name="server-host2-RC" group="main-server-group" auto-start="true"> <jvm name="default"> ............. <jvm-options> </jvm> <socket-bindings socket-binding-group="ha-sockets" port-offset="0"/> </server> </servers> Now when I say its not working as expected, when we test failover, I mean - the communication of RC and SL is broken. After the communication is broken, we have currently a workaround -restarting the RC and SL on cluster, which makes it work as before. By the way RC communicates with SL on port 6080 via http. RC communicates with JMS on SL (JMS JNDI url:http-remoting://<ip address of SL which is Node1>:6080/) Just a note:- everything is working properly in production if we don't try the failover testing scenario by disabling network or powering off etc. Let me know if you need any other info. Thanks, Preeta was (Author: kpreeta12): The cluster that we have is a domain managed cluster where we have domain.xml and host.xml configured on Node1 and only host.xml configured on Node2. The jgroups is a subsystem in the domain.xml for the profile "ha". Regarding our application, we have 2 components - RC.war and SL.war. The JMS is configured on SL. Only component RC is clustered. SL is not clustered. Node 1 has - 2 server instances- RC and SL. <servers> <server name="server-host1-RC" group="main-server-group" auto-start="true"> <jvm name="default"> <heap size="2048m" max-size="2048m"/> <permgen size="512m" max-size="512m"/> <jvm-options> <!--<option value="-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"/>--> <option value="-XX:CompileCommand=exclude,com/newscale/bfw/signon/filters,AuthenticationFilter"/> <option value="-XX:CompileCommand=exclude,org/apache/xml/dtm/ref/sax2dtm/SAX2DTM,startElement"/> <option value="-XX:CompileCommand=exclude,org/exolab/castor/xml/Marshaller,marshal"/> <option value="-XX:CompileCommand=exclude,org/exolab/castor/xml/Marshaller,marshal"/> <option value="-XX:CompileCommand=exclude,org/apache/xpath/compiler/XPathParser,UnionExpr"/> </jvm-options> </jvm> <socket-bindings socket-binding-group="ha-sockets" port-offset="0"/> </server> <server name="server-host1-SL" group="other-server-group" auto-start="true"> <jvm name="default"> <heap size="2048m" max-size="2048m"/> <permgen size="512m" max-size="512m"/> <jvm-options> <option value="-server"/> </jvm-options> </jvm> <socket-bindings socket-binding-group="standard-sockets" port-offset="0"/> </server> </servers> Node 2 : has only one server instance and that has RC <servers> <server name="server-host2-RC" group="main-server-group" auto-start="true"> <jvm name="default"> <heap size="2048m" max-size="2048m"/> <permgen size="512m" max-size="512m"/> <jvm-options> <!--<option value="-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"/>--> <option value="-XX:CompileCommand=exclude,com/newscale/bfw/signon/filters,AuthenticationFilter"/> <option value="-XX:CompileCommand=exclude,org/apache/xml/dtm/ref/sax2dtm/SAX2DTM,startElement"/> <option value="-XX:CompileCommand=exclude,org/exolab/castor/xml/Marshaller,marshal"/> <option value="-XX:CompileCommand=exclude,org/exolab/castor/xml/Marshaller,marshal"/> <option value="-XX:CompileCommand=exclude,org/apache/xpath/compiler/XPathParser,UnionExpr"/> </jvm-options> </jvm> <socket-bindings socket-binding-group="ha-sockets" port-offset="0"/> </server> </servers> Now when I say its not working as expected, when we test failover, I mean - the communication of RC and SL is broken. After the communication is broken, we have currently a workaround -restarting the RC and SL on cluster, which makes it work as before. By the way RC communicates with SL on port 6080 via http. RC communicates with JMS on SL (JMS JNDI url:http-remoting://<ip address of SL which is Node1>:6080/) Just a note:- everything is working properly in production if we don't try the failover testing scenario by disabling network or powering off etc. Let me know if you need any other info. Thanks, Preeta -- This message was sent by Atlassian JIRA (v6.4.11#64026)