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

Murtaza Ghodawala (JIRA) jira-events at lists.jboss.org
Tue Feb 12 00:25:56 EST 2013


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

Murtaza Ghodawala reopened AS7-6496:
------------------------------------



Hi Tomaz and Brian,

I understand what you are suggesting - from your comments I infer that we shouldn't add any <server>xml tag under <servers>parent xml tag. Please correct my understanding.

Also, in addition to the above problem, I was also expecting resolution for the below problems. Appreciate if you can help in that also -

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

Resolution - 

As per Brian and Tomaz, I shouldn't configure any <server> tag under parent <servers> tag. 

But my main concern is whether putting this <server> tag only in SLAVE JBOSS hosts.xml will be enough to replicate the archives deployed from console? 


2. Server group should be independantly created in SLAVES.

Can this be possible? Since domain.xml of master JBOSS is being used in all the SLAVES and server groups are created in domain.xml. Is there any possibility of doing this?

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

This is the utmost concern. What does this exceptions mean? What are the implications, this exceptions has almost filled half of our logs. Please suggest how to remove this exception. It is always coming for "server-two" even though we have not deployed any archives on this server since it is a part of main-server-group.


[Server:server-two] 08:19:22,562 WARN  [com.arjuna.ats.jta] (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
                
> 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


More information about the jboss-jira mailing list