[jboss-jira] [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422118#action_12422118 ] 

Brian Stansberry commented on JBAS-5284:
----------------------------------------

The EJB disclaimer was in reference to this discussion in http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/beta422/html/ch05s11s03.html

"On the other hand, the barrier-dependent service will be instantiated/created (i.e., any create() method invoked) on all nodes, but only started on the master node. This is different with the deploy-hasingleton approach that will only deploy (instantiate/create/start) the contents of the deploy-hasingleton directory on one of the nodes.

So services depending on the barrier will need to make sure they do minimal or no work inside their create() step, rather they should use start() to do the work. "

Also this from http://wiki.jboss.org/wiki/HASingletonDeployer

"Please Note: the Barrier controls the start/stop of dependend services, but not their destruction (this happens only when the BarrierController is itself destroyed/undeployed). Thus using the Barrier to control services that need to be "destroyed" as part of the normal Barrier operation (like the EJBContainer) will not have the desired effect."

> Cannot use a scoped loader repository in deploy-hasingleton deployments
> -----------------------------------------------------------------------
>
>                 Key: JBAS-5284
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5284
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>
> If you try to add a loader-repository element to a deploy-hasingleton deployment, you get something like this:
> Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: jboss.dataintegration:sar=dataintegration.sar, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
> I suspect this is because the deploy-hasingleton dir itself is being treated as the root deployment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira