We have analyzed that JBOSS MASTER has some issues and tried to login to Console. Below is the error I am receiving in the logs of JBOSS MASTER -

[Server:server-two] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [jbossjts-4.16.2.Final.jar:]
[Server:server-two] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-4.16.2.Final.jar:]
[Server:server-two] Caused by: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected)
[Server:server-two] at org.hornetq.core.client.impl.ServerLocatorImpl.assertOpen(ServerLocatorImpl.java:1823) [hornetq-core-2.2.13.Final.jar:]
[Server:server-two] at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:699) [hornetq-core-2.2.13.Final.jar:]
[Server:server-two] at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.connect(HornetQXAResourceWrapper.java:321) [hornetq-jms-2.2.13.Final.jar:]
[Server:server-two] at org.hornetq.jms.server.recovery.HornetQXAResourceWrapper.getDelegate(HornetQXAResourceWrapper.java:251) [hornetq-jms-2.2.13.Final.jar:]
[Server:server-two] ... 7 more
[Server:server-two]

Also, due to heavy load of user request, JBOSS Master console was not working until all requests are served. We are expecting a suggestion to overcome this shortcoming -

1. Deployments of archives should be done only on SLAVES and not on MASTER (domain controller).

2. Server group should be independantly created in SLAVES.

3. Periodic recovery error in Master JBOSS shouldn't occur -

(Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery