[JBoss JIRA] Created: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
4:06 p.m.
Cannot use a scoped loader repository in deploy-hasingleton deployments
-----------------------------------------------------------------------
Key: JBAS-5284
URL: http://jira.jboss.com/jira/browse/JBAS-5284
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: Brian Stansberry
Assigned To: 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
Galder Zamarreno commented on JBAS-5284:
----------------------------------------
Hmmm, I've managed to deploy HASingleton barrier EJB3 beans without any issues.
What issues are you refering to with "Note that this will not work properly for EJB
deployments."?
Also, as a side note, I see that jboss-app has <depends/> missing. Scott says the
following in: http://www.jboss.com/?module=bb&op=viewtopic&t=96686&start=10
"jboss-app.xml does not support depends because its not a component deployment.
Its more of a packing notion. Anything needing a dependency in an ear would have its
own depends support in its descriptor. "
Wouldn't it make sense to have a <depends/> for an EAR indicating that the EAR
can
be deployed as a singleton without putting it in deploy-hasingleton? That probably
be a preferred way to deploy an EAR as singleton.
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
1:14 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
Adrian Brock closed JBAS-5284.
------------------------------
Resolution: Rejected
You can't use a loader repository in deploy-hasingleton
because it is deploying the whole directory as a single deployment.
If you want individual deployments then should make
deploy-hasingleton-service.xml deploy a URLDeploymentScanner
such that it deploys individual applications in deploy-hasingleton.
e.g. Change the start/stop in deploy-hasingleton-service.xml to
deploy the deployment scanner (see below - hasingleton-scanner-service.xml)
<attribute name="TargetStartMethod">deploy</attribute>
<attribute
name="TargetStartMethodArgument">${jboss.server.home.url}/hasingleton-scanner-service.xml</attribute>
<attribute name="TargetStopMethod">undeploy</attribute>
<attribute
name="TargetStopMethodArgument">${jboss.server.home.url}/hasingleton-scanner-service.xml</attribute>
Then create a server/all/hasingleton-scanner-service.xml
with something contents like (i.e. scan and deploy the contents of deploy-hasingleton).
<server>
<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
name="jboss.deployment:type=DeploymentScanner,flavor=URL,name=HASingleton">
<depends
optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
<attribute
name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
<attribute name="FilterInstance"
attributeClass="org.jboss.deployment.scanner.DeploymentFilter"
serialDataType="javaBean">
<!-- Files starting with theses strings are ignored -->
<property name="prefixes">#,%,\,,.,_$</property>
<!-- Files ending with theses strings are ignored -->
<property name="suffixes">#,$,%,~,
\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh</property>
<!-- Files matching with theses strings are ignored -->
<property
name="matches">.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags</property>
</attribute>
<!-- Frequency in milliseconds to rescan the URLs for changes -->
<attribute name="ScanPeriod">5000</attribute>
<!-- A flag to disable the scans -->
<attribute name="ScanEnabled">true</attribute>
<!-- HERE !!!!!!!!!! Hot deploy hasingleton as individual
applications -->
<attribute name="URLs">
deploy-hasingleton/
</attribute>
<attribute name="RecursiveSearch">True</attribute>
</mbean>
</server>
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
4:24 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
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/Cl...
"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
4:24 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-5284:
----------------------------------------
LOL. I was going to change this to Fix Version Backlog, since it's a solvable problem
but wasn't anywhere on my radar screen. But just rejecting it seems more honest.
In AS 5, deploy-hasingleton content is presented individually to the ProfileService, so
this shouldn't be an issue (although I haven't tested it.)
I don't believe undeploying a URLDeploymentScanner causes an undeployment of
previously deployed content. This could be added to a subclass by overriding stopService,
clearing the urlList and doing one more scan.
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
4:52 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5284) Cannot use a scoped loader repository in deploy-hasingleton deployments
[
https://jira.jboss.org/jira/browse/JBAS-5284?page=com.atlassian.jira.plug...
]
Adrian Brock commented on JBAS-5284:
------------------------------------
"I don't believe undeploying a URLDeploymentScanner causes an undeployment of
previously deployed content."
You mean stopping.
We'll that's a bug then :-)
https://jira.jboss.org/jira/browse/JBAS-5790
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
5904
days inactive
6041
days old
5 comments
3 participants
participants (3)
-
Adrian Brock (JIRA) -
Brian Stansberry (JIRA)
-
Galder Zamarreno (JIRA)