[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2625) add an "application stop/application start" option to jboss server view

Francisco Jose Peredo Noguez (JIRA) jira-events at lists.jboss.org
Fri Aug 15 23:14:58 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBIDE-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12425326#action_12425326 ] 

Francisco Jose Peredo Noguez commented on JBIDE-2625:
-----------------------------------------------------

It is  not enough  (the "Touch" icon in the toolbar is great, I haven't noticed it, but I have been wishing for it) because, if the application is failing because of an infinite loop that is leaking memory (or sending corrupt data to de development database, or using the processor upt to 99%) what one wants is to stop it first, and then, decide, without a hurry, how to fix it, perhaps that will take 5, 10 or 30 minutes, and if the application is not stopped while we are thinking of a solution, it might end up crashing JBoss AS, or filling the development database with garbage, those are both cumbersome and time wasting outcomes.

Right now, the only way to deal with this kind of problem is to stop all the appserver, I wish I could stop just the offending application (and I know it is possible, because in Netbeans one can stop, and even undeploy a particular application without stopping all the app server) I wish I could do that in Eclipse.

> add an "application stop/application start" option to jboss server view
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-2625
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2625
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>    Affects Versions: 2.1.2
>            Reporter: Francisco Jose Peredo Noguez
>
> 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 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

        



More information about the jbosstools-issues mailing list