August 2010 - jboss-dev-forums - Jboss List Archives

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559865#559865 -------------------------------------------------------------- > > Brian meant a different file, and they shouldn't necessarily be poking in the data area, which I admit is not intuitive. That's a very good point. It's also inconsistent with the exploded dir, which preserves the original. We could alternatively leave the file there and just add the .deployed as an indicator that it was deployed. The only side effect is that it would require a copy vs a move, but IMO not a huge deal for zips. > If you leave the original archive in place, I think there is little point having a marker file there hanging. Logs/console/cli should tell you if a deployment was successfull or not and for index purposes or otherwise you can always keep state somewhere else, outside the users view. > > Unless you want to have archives in ./deploy and not wanting them to deploy? (but then why have them there in first place) Yes the state could be stored elsewhere, basically a timestamp and file size should be sufficient to determine if the file has indeed changed. It's only value with the copy approach is to provide a quick indication that something is currently deployed. > Now, regarding exploded deployments, why not using the containing directory to be the marker itself? "Touching" the upper level directory conceptually is similar to touching a zipped archive. Although it's not so straightforward to do on Windoze. That still doesnt solve the undeploy problem, where the content will disappear out from under the classloader and cause frameworks like seam to fail. It also doesn't help the problem where atomic moves aren't possible for one reason or the other. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559865#559865] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Dimitris Andreadis

Dimitris Andreadis [http://community.jboss.org/people/dimitris%40jboss.org] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559862#559862 -------------------------------------------------------------- > Jason Greene wrote: > > > jaikiran pai wrote: > > > > Nice! :) > > > > Here's some questions I have: > > > Brian Stansberry wrote: > > > > > > *For zipped archives*: > > > Scanner will detect an archive in the hot-deploy dir, e.g. hot-deploy/foo.war. Scanner will use the same https://community.jboss.org/thread/155937?tstart=0 deployment API that an external client would use to register the content with the server and deploy it. Once the content is registered the server will maintain it's own copy in an internal directory (e.g. server/data/deployments). Scanner will replace the hot-deploy/foo.war file with a simple marker file hot-deploy/foo.war.deployed. > > Would it be a "rename" or would the foo.war.deployed be a completely different file? From what I understand, I believe it would be a completely different file without any .war semantics, but just wanted to be sure. Furthermore, where would be original foo.war be moved to? Are users expected to know where it's moved to? If not, then they probably will have to maintain a copy of their original deployment somewhere (I know most of them already do that, but again I just wanted to be clear about the expectations). > > > Brian meant a different file, and they shouldn't necessarily be poking in the data area, which I admit is not intuitive. That's a very good point. It's also inconsistent with the exploded dir, which preserves the original. We could alternatively leave the file there and just add the .deployed as an indicator that it was deployed. The only side effect is that it would require a copy vs a move, but IMO not a huge deal for zips. If you leave the original archive in place, I think there is little point having a marker file there hanging. Logs/console/cli should tell you if a deployment was successfull or not and for index purposes or otherwise you can always keep state somewhere else, outside the users view. Unless you want to have archives in ./deploy and not wanting them to deploy? (but then why have them there in first place). Now, regarding exploded deployments, why not using the containing directory to be the marker itself? "Touching" the upper level directory conceptually is similar to touching a zipped archive. Although it's not so straightforward to do on Windoze. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559862#559862] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559855#559855 -------------------------------------------------------------- True! Argh; I tried to rename this thread to "Thoughts on filesystem action based hot deployment" since that's a big enough topic by itself. But that just changed the title of the first post. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559855#559855] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - JBPM-2889 - support for cron expression in timer

by Alejandro Guizar

Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] replied to the discussion "JBPM-2889 - support for cron expression in timer" To view the discussion, visit: http://community.jboss.org/message/559851#559851 -------------------------------------------------------------- Sounds like a neat feature - I'll be sure to take a look at it. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559851#559851] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss ESB Development] - Naming for webservice endpoints

by Tom Fennelly

Tom Fennelly [http://community.jboss.org/people/tfennelly] replied to the discussion "Naming for webservice endpoints" To view the discussion, visit: http://community.jboss.org/message/559843#559843 -------------------------------------------------------------- Of course another option for SOAPProxy... you could leave the existing "wsdl" property format as is and add support for a new (alternative) property that has exactly the same name and value format as the SOAPProcessor i.e. support 2 options. URI: <action ...> <property name="wsdl" value="http://...."/> ... etc </action> and, endpoint ObjectName... <action ... class="org.jboss....SOAPProxy"> <property name="jbossws-endpoint" value="foo:HelloWorldWS"/> ... etc </action> Raise an error if both are configured. Just say'n. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559843#559843] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Alexey Loubyansky

Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559828#559828 -------------------------------------------------------------- My opinion is if CLI is what we will have to add sooner or later anyway and it might be a more intuitive way than the deploy dir then I would start with CLI. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559828#559828] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Alexey Loubyansky

Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559824#559824 -------------------------------------------------------------- Actually, be it CLI-based, prorgammatic or deploy dir - it's all hot deploy, right? It's just CLI is not the original JBoss deploy dir style hot deploy. Hot deploy means being able to deploy w/o server restart. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559824#559824] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559819#559819 -------------------------------------------------------------- > Alexey Loubyansky wrote: > > > *Ultimately we really should push people to using the CLI because then we can get truly intuitive behavior.* > Why not start with CLI then? And if needed add a deploy dir-based one later? That has always been my preference. However, many think we should preserve it, and I am certainly sympathetic to it. I guess really what we need to figure out is can we find the magic balance of trade-offs that makes it intuitive enough, but still not cause application crashes. Note that for reference Glassfish uses a similar marker file approach, and I haven't heard any major complaints from it. One thing we could also do is ship a HOWTO file in that directory that tells you the semantics. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559819#559819] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Brian Stansberry

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559818#559818 -------------------------------------------------------------- That's a fair question in terms of organization of work. I think hot deploy is on the agenda because: 1) We have a mini-goal of recreating the functionality of the AS 6 'minimal' profile which includes hot deployment. 2) When thinking about the deployment API and the implementation we need to think about hot deployment, to make sure we cover the requirements. #2 is IMHO much more important; mini-goals like #1 should shift to match whatever is most productive in getting to the overall M1 goals. But if once we feel comfortable we've adequately considered hot deployment, I have no problem focusing on CLI or programatic deployments. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559818#559818] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene%40jboss.com] replied to the discussion "Thoughts on hot deployment" To view the discussion, visit: http://community.jboss.org/message/559813#559813 -------------------------------------------------------------- > jaikiran pai wrote: > > Nice! :) > > Here's some questions I have: > > Brian Stansberry wrote: > > > > *For zipped archives*: > > Scanner will detect an archive in the hot-deploy dir, e.g. hot-deploy/foo.war. Scanner will use the same https://community.jboss.org/thread/155937?tstart=0 deployment API that an external client would use to register the content with the server and deploy it. Once the content is registered the server will maintain it's own copy in an internal directory (e.g. server/data/deployments). Scanner will replace the hot-deploy/foo.war file with a simple marker file hot-deploy/foo.war.deployed. > Would it be a "rename" or would the foo.war.deployed be a completely different file? From what I understand, I believe it would be a completely different file without any .war semantics, but just wanted to be sure. Furthermore, where would be original foo.war be moved to? Are users expected to know where it's moved to? If not, then they probably will have to maintain a copy of their original deployment somewhere (I know most of them already do that, but again I just wanted to be clear about the expectations). > Brian meant a different file, and they shouldn't necessarily be poking in the data area, which I admit is not intuitive. That's a very good point. It's also inconsistent with the exploded dir, which preserves the original. We could alternatively leave the file there and just add the .deployed as an indicator that it was deployed. The only side effect is that it would require a copy vs a move, but IMO not a huge deal for zips. > > Brian Stansberry wrote: > > > > User can trigger a replacement of foo.war (undeploy old, deploy new) by copying a new foo.war into hot-deploy/ > Later in your post, I see that special care has to taken to avoid spurious hot deploys (i.e. picking up a deployment even before it is completely copied to hot-deploy folder) for exploded deployments. How do we handle such cases for these zipped archives? i.e. What happens when a zipped foo.war is still being copied to hot-deploy and the scanner picks it up for deployment? What I had in my head for that scenario, was that we would just detect an incomplete zip, and wait for the next few intervals before reporting the failure. It's pretty easy to do this because zip files store the directory at the end. > *Nested deployments:* > > In case of nested deployments, I believe only the top level META-INF/jboss.deploy marker file plays a role. Any marker files in sub-deployments of the top-level deployment, will +not+ have any effect on the hot-deploy semantics. Am I right? > > > Finally, are the *.deployed and jboss.deploy marker file semantics only specific to a hot deployment enabled folder (like hot-deploy)? Considering a simple foo.war zipped archive in a normal deploy folder (without hot deployment), would it too be replaced with a marker foo.war.deployed file? And would jboss.deploy play a role in exploded deployment in a normal deploy folder? Correct. We would basically treat the outer deployment as an atomic entity, and only look for the markers relevant to it. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/559813#559813] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2010