Stan Silvert [http://community.jboss.org/people/ssilvert] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593521#593521 -------------------------------------------------------------- Guys, I'm sorry if I sounded overly-critical yesterday.  I realize that I've only been working on AS7 a few weeks while some of you have been putting in long hours on it for months and months.  There's a lot of really great stuff in AS7 but I don't think we want the user's first impression to be a turn-off.  I've seen this sort of thing kill great software in the past and we really, really need to get it right. So I ask you to take advantage of my perspective here, which is as one who is coming to the product with little knowlege of how or why certain decisions were made.  I just want to deploy something. So this morning I downloaded the beta and tried to do just that.  I tried to deploy something.  I see the README file that talks about "dodeploy" files.  So my earlier criticism about how I would know about it is somewhat alleviated. But here is how it turned out: 1) Download AS 2) Drop my WAR in standalone/deployments  3) Start AS Nothing happens.  Decide it's time to look at the README.  (BTW, the README says "/deployment" but the dir name is plural "/deployments") 1) Create a "dodeploy" file. 2) Start AS Nothing happens.  I notice that my dodeploy file name is misspelled.  The WAR name is a little long and complicated, so that's not surprising.  But I'm annoyed at the fact that I had to type it and now I have to fix it. 1) Fix the file name 2) Start AS Nothing happens except that I get this warning: 09:08:26,174 WARN  [org.jboss.as.deployment] (pool-6-thread-1) Deployment of 'C: \jboss-7.0.0.Beta1\standalone\deployments\mojarra2.0-notbundled.war.dodeploy' re quested, but the deployment is not present But I know the deployment is there!  Maybe I should touch the dodeploy.  I can't do that from Explorer so I have to open a command prompt.  There is no "touch" command on Windows, but luckily I have Cygwin in my path for just such occasions.  Woops!  I can't touch what isn't there.  My dodeploy file is gone!!  Where did it go? Let's take the README a more literally.  Instead of creating a dodeploy file and starting the server, let's try starting the server and actually issuing the touch command from the command prompt. 1) Start AS 2) cd to standalone/deployments 3) touch my-long-funky-war-name.war.dodeploy It finally deploys!! Pretending that I'm a developer seeing AS7 for the first time, what's my impression?  Love the quick boot time.  Hate the deployment mechanism.  Fix the latter and I'm very, very happy. Stan -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593521#593521] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/594134#594134 -------------------------------------------------------------- AIUI, the bug is Stan mistyped the file name. :-) The question is whether deleting the wrnog-spelling.dodeploy is the right thing to do. The scanner deletes extraneous marker files as a matter of housekeeping. That behavior could be removed, but I'd argue that in this case, it's disconcerting but somewhat helpful. The file is gone, forcing the user to try again and maybe get it right. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/594134#594134] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jason Greene [http://community.jboss.org/people/jason.greene] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/594243#594243 -------------------------------------------------------------- Stan, Are you running a current version? The console log tells you the file you need to create. If it's fresh boot the messagebis a little too early. We can look at ways to make it more noticeable. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/594243#594243] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dimitris Andreadis [http://community.jboss.org/people/dimitris] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593560#593560 -------------------------------------------------------------- When it comes to marker names without a uniqueness issue I'd go for: .skipdeploy .isdeploying .deployed .failed .isundeploying .undeployed -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593560#593560] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolfgang Knauf [http://community.jboss.org/people/WolfgangKnauf] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/598333#598333 -------------------------------------------------------------- Sorry for coming up with a user question here, but I observe a "strange" behavior with auto deployment: I copied an EAR file to the "standalone\deployments" directory (using a JBoss picked from GIT two hours ago). Deployment fails and a "..ear.failed" file is created. So I tried to "undeploy" the app by killing the "...ear.failed" file. But this resulted in a undeploy and redeploy of the EAR (with another failure of course). Is this the expected behaviour? In case of an error, is it possible to just delete the EAR file and the "ear.failed" file to remove the app from the server? If yes, it would be worth to add this to "README.txt" ;-). Best regards Wolfgang -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/598333#598333] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolfgang Knauf [http://community.jboss.org/people/WolfgangKnauf] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/598603#598603 -------------------------------------------------------------- Thanks for the clarification, Brian. Another "strange" thing: I have a small app (working fine on AS5), where I get a ".failed" file with this text: "Failed to execute deployment operation in allowed timeout [60]" (I don't know why, will be tracked elsewhere - but it seems to be a good testcase for autodeploy robustness ;-)) . So I delete the ear file once again. The ".failed" file also disappears. But in "\jboss-7.0.0.Beta3-SNAPSHOT\standalone\configuration\standalone.xml", I still see this:     <deployments>         <deployment name="Stateless.ear" runtime-name="Stateless.ear" sha1="d8aa82f2731236f3ed0b53fca26f35eb0c9c0bc6"/>     </deployments> Stopping and restarting the server will bring those errors (the errors point to modules in "Stateless.ear"): 21:46:08,937 ERROR [org.jboss.as] (MSC service thread 1-3) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" started (with errors) in 4281ms - Started 550 of 584 services (2 services failed or missing dependencies, 32 services are passive or on-demand)     Services missing dependencies:         service jboss.naming.context.java.module.Stateless.StatelessWeb."env/de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelServlet/geometricModel"         service jboss.naming.context.java.module.Stateless.StatelessWeb."env/de.fhw.komponentenarchitekturen.knauf.stateless.GeometricModelServlet/geometricModelLocal" The sample app can be found here: http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stat... http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/stateless/Stat... Best regards Wolfgang -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/598603#598603] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jason Greene [http://community.jboss.org/people/jason.greene] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/598609#598609 -------------------------------------------------------------- Are you volunteering? :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/598609#598609] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/598635#598635 -------------------------------------------------------------- David Lloyd argued against the .failed files essentially because of the problem you raise. The true representation of the state of the server is in the standalone.xml file, not in these marker files. The FS scanner is a client to the core server in pretty much the same way that a user using the CLI is and the someone using web console will be. It detects changes on the filesystem, makes requests to the core server management layer and the writes up .failed, .deployed etc based on what it response it gets. Those files represent the client view of the system though; if the server doesn't respond, the FS scanner eventually gives up and marks a failure. But because the server didn't respond the FS scanner doesn't really know the true state on the server side. The server isn't responding probably due to JBAS-9010, which is being worked. The "Failed to execute deployment operation in allowed timeout [60]" message needs to be beefed up to make it clear that this is an anomalous situation, the scanner doesn't know what happened, and the user needs to investigate and clean up. https://issues.jboss.org/browse/JBAS-9020 https://issues.jboss.org/browse/JBAS-9020 will help with the cleanup issue. Currently we don't track where deployment content comes from, and we treat all content the same, whether it was scanned in from deployments/ or installed into the system via CLI or web console. As a result, following reboot we lose track of whether stuff that was installed by the scanner is no longer present and needs to be undeployed. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/598635#598635] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/599649#599649 -------------------------------------------------------------- If auto-deploy is enabled, yes, either removing the .failed file or adding a .dodeploy file will trigger deployment. Putting down a .dodeploy is equivalent to invoking a command; we'll try and carry out the command. The .dodeploy file is deleted when the operation either succeeds or fails. The scanner tells the management layer to do the deployment but to roll it back if the deployment layer reports a failure. So if it the deployment layer reports a failure, the deployment should not appear in standalone.xml.. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/599649#599649] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/599928#599928 -------------------------------------------------------------- Can you file a JIRA?  Even better, with a patch. :-) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/599928#599928] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Wolfgang Knauf [http://community.jboss.org/people/WolfgangKnauf] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/600785#600785 -------------------------------------------------------------- One more question: today's server from GIT made my sample EARs deploy, but there was an error in the web modules. In spite of this error, a "Stateless.ear.deployed" file was created and the ear was added to "standalone.xml". I would expect to cause the full deployment to fail if any module fails. Or is this misunderstanding of mine ;-)? And if partial modules can fail, but the full deployment is considered "OK", a status file for each module would be nice, e.g. "Stateless.ear_Stateless.war.failed" or something similar. But this might break all the rest of the deployment concept... By the way: it seems the app was no longer undeployed when I deleted the ear file on disk? At least the ".deployed" file and the entry in "standalone.xml" was left. And when deleting it, a ".undeployed" file was created and left behind. Best regards Wolfgang -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/600785#600785] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593511#593511 -------------------------------------------------------------- I'll leave that question to someone who knows more about how this is currently handled in AS7. I kind of know that the contents are copied over to data/content folder. But I don't know the exact details from a developer point of view. Ideally, if at all we want to use marker files, it would be good to reduce the number of marker files that the users should be aware about. IMO, the user could continue using the AS 4.x (and 5.x) approach of redeploying, by updating the real deployment file. Again, if he wants to disable that redeployment till it's completely copied, he can first copy a .skipdeploy (just like a normal deploy operation). -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593511#593511] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]