[
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.
add an "application stop/application start" option to jboss
server view
-----------------------------------------------------------------------
Key: JBIDE-2625
URL:
https://issues.jboss.org/browse/JBIDE-2625
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
Sometimes, and application just enters an infinte loop (because of a programming error,
because it can not find a class, etc) in those cases one has to stop all the application
server but sometimes, the problem can be solved simply by stopping that particular
application, fixing the problem, and starting it again, and, since one didn't have to
restart Jboss, it takes a lot less time. I would like to be able to do that in an easy way
from inside eclipse.
--
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