[jboss-jira] [JBoss JIRA] (AS7-6496) Domain Controller shouldn't serve user request and it shouldn't store deployment archives (WAR)

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved AS7-6496.
-----------------------------------

    Resolution: Rejected


If you don't want your master HostController to run any servers, don't configure any in its host.xml. We ship an example host-master.xml that illustrates this. 

There are legitimate reasons to allow the master HC to runs servers, particularly in development and demo environments where quickly spinning up a couple servers is nice. So we won't be removing that capability. I agree that having the master HC run servers is not advisable in a production environment.

Note also that the console logging you see when you run domain.sh is not solely from the HostController process. The console aggregates logging from all the processes that are spawned as a result of running domain.sh. The process that is doing the logging can be identified via the beginning of the log message, e.g. "[Server:server-two]".
                
> Domain Controller shouldn't serve user request and it shouldn't store deployment archives (WAR)
> -----------------------------------------------------------------------------------------------
>
>                 Key: AS7-6496
>                 URL: https://issues.jboss.org/browse/AS7-6496
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.1.Final
>         Environment: PRODUCTION
>            Reporter: Murtaza Ghodawala
>            Assignee: Brian Stansberry
>            Priority: Critical
>              Labels: DOMAIN_CONTROLLER
>
> 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

--
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