I observerd the following while doing test. please let me if you have solution to this. I setup domain in a single PC (no slave configuration) to test clustering with appache httpd.
A). to cluster to be correctly operate, socket group name of the
server group where the profile name=”full-ha”,must be “full-ha-sockets”.The bare minimum requirement is “ha-sockets”though it doesn’t correctly operate the “failover” concept. (if one server is down it will stop responding to user requests and the other servers in the cluster will not serve the requests). Additionally server start with errors (dependency issues) as follows.
JBAS014775: New missing/unsatisfied dependencies:
service jboss.binding.jacorb (missing) dependents: [service jboss.jacorb.orb-service]
service jboss.binding.jacorb-ssl (missing) dependents: [service jboss.jacorb.orb-service]
service jboss.binding.messaging (missing) dependents: [service jboss.messaging.default]
service jboss.binding.messaging-throughput (missing) dependents: [service jboss.messaging.default]
B). To operate on “full-ha-sockets”,you cannot “auto-start” more than one server in the server group. If you do, it will create a deadlock situation.
ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 18599604, [id: 0x011bceb4, localhost/127.0.0.1:5695])) Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER]
at org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:126) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:807) [hornetq-core-2.2.13.Final.jar:]
at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:187) [hornetq-core-2.2.13.Final.jar:]
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) [netty-3.2.6.Final.jar:]
C) Even after you start the server and try to start other servers in the group through admin console, it will enter to deadlock state.
However difference between “full-ha-sockets”and “ha-sockets” configuration is “full-ha-sockets” configuration still operate and serve the user request in this situation. (Server which is auto started at boot, will continuously serve the request unless you stop this server, and keep other in the same server group).