[ https://jira.jboss.org/jira/browse/JBIDE-2625?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2625: -------------------------------------------- And the "Touch" icon in the toolbar that touches the descriptors to ensure app restart is not enough ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2625?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2625: -------------------------------------------- I've never heard about a way in any java or jboss app to forcefully stop just one part of the deployment. If you could tell me how netbeans does it then I would like to hear. For now I don't know of other techniques than "touch descriptors" for restart and undeploy to make the app not continue to run (existing threads will of course still execute since java does not support killing internal threads) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2625?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2625: -------------------------------------------- Yes, I know about stop(), but I do not think it will stop executing existing threads... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2625?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2625: --------------------------------------- Component/s: JBossAS Fix Version/s: LATER -- 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

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-2625: ------------------------------------ Couldnt you just... undeploy the application? I realize you'd rather stop and then decide, but, couldn't you just... remove the module from the server and republish it 10-20 minutes later when you figure out how to fix it? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-2625: ------------------------------------ It seems that this might not be possible currently. JBoss 4.2 does have the mbean under jboss.j2ee, service=EARDeployment,url='MyApp.ear', however telling it to 'stop' doesn't seem to do a damn thing. I can still visit the servlet and it still will serve out html files. So sstopping this mbean seems like it doesn't do anything at all. In JBoss 5.0, that MBean doesn't even exist. And JBoss 7 does not have mbeans. For 5.0, I was unable to find other mbeans that are able to do it and actually stop an app. This doesn't seem as easy as I had expected and in fact I doubt that it is even universally accessible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-2625: -------------------------------------------- this should all be avaiable through AS 7 api - putting on beta1 for review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-2625 at 11/9/11 8:21 AM: ------------------------------------------------------------------ I have looked into the current API and I cannot find a way to disable/enable a deployment. The admin guide at https://docs.jboss.org/author/display/AS71/Admin+Guide#AdminGuide-Deploym... only mentions deploy/undeploy commands. Afaik undeploy does not remove deployment, it just 'disables' it. Do we need functionality that goes beyond what deploy/undeploy does so far? was (Author: adietish): I have looked into the current API and I cannot find a way to disable/enable a deployment. I only see deploy/undeploy commands and I guess that this is the only thing that is available. Undeploy could still not remove the deployment just 'disable it'. Do we need functionality that goes beyond what deploy/undeploy does so far? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-2625: ------------------------------------ Thus far, our research has shown that our servers do not support "stopping" a deployment while leaving it in running memory. AS7 (as far as we know) does not support stopping a deployment, only undeploying it. Undeploying a deployment unit removes it from memory but leaves it on the disk. There is no way to leave the deployment in memory and temporarily stop it and its threads from responding to requests. Previous versions of the app server have mbeans that have a 'stop' command associated with them, but these actions do not seem to stop the deployment from running or responding in any way at all. User does not have to shut down the entire app server. He only needs to undeploy the offending application. We could make 'stop' effectively initiate an undeploy behind the scenes, but there is limited benefit to this except a minor enhancement to the user's workflow when they want to restart / redeploy the application. They would no longer need to go "add / remove from server" or "run on server" to re-add it to the server, only "start" again (causing a new redeploy). The web GUI has a similar pattern, labeling the eclipse "start/stop" as "enable/disable" (effectively causes an deploy / undeploy inside the app server). It also has "add / remove" which delete or re-add all artifacts to/from the filesystem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-2625: ----------------------------------------- I now talked to emuckenhuber and he basically told me there was add/remove and deploy/undeploy. deploy/undeploy are not tackling with the artifact. they just undeploy but do not remove the war from the file system. Add/Remove do that actually. Remove removes the war from the file system. The Web-GUI pretty much confirms this: !web-gui.png! If you hit Add you'll get a file dialog that allows you to choose a depolyment artifact. In the end the war shows up and is enabled. If you hit "enabled" as7 will undeploy the war (but not remove the war from the filesystem): {code} 15:01:55,916 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 8) Undeployed "test.war" {code} Hitting "Remove" will remove the war from the deployment directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-2625: --------------------------------------- Fix Version/s: 3.3.0.Beta2 (was: 3.3.0.Beta1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-2625?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-2625: ------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) -- 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