[ https://issues.jboss.org/browse/JBIDE-7753?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-7753: ------------------------------------ It seems to work for me. If the server is fully started, it shuts down properly... -- 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-7753?page=com.atlassian.jira.plugin... ] Dominik Pospisil commented on JBIDE-7753: ----------------------------------------- However, the AS5 based runtimes does not work for me as well, investigating... -- 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-7753?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-7753: ------------------------------------ Dominik: I've looked through it and from what I can tell, it works properly when a proper server home is selected in teh server editor. Using default values for remote server home is impossible since there is no standard as to where all machines should keep their remote server. As per the ServerBehaviourDelegate.stop(etc) javadoc, there is no easy way to communicate an error here. The javadoc is pasted below. There was an error that I was not accounting for. So when you add these two together, it was silently erroring and ignoring it. I've changed the default text field value for new RSE servers or anywhere server home is null to be a string "SERVER HOME HERE" or some such visible thing to indiciate this is not a proper value. After making these changes, and properly setting an accurate server home, stop still seems to work fine for me. Now when it fails, it will log an error to the error log view, however the error log view doesn't seem to pop up right away, which seems strange to me. A different error is popped up via the servertools framework but as teh javadoc notes, there is no way for me to add my input to it. * [issue: There is no way to communicate failure to the * client. Given that this operation can go awry, there probably * should be a mechanism that allows failing async operations * to be diagnosed.] -- 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-7753?page=com.atlassian.jira.plugin... ] Dominik Pospisil commented on JBIDE-7753: ----------------------------------------- Failing with pipe closed error as it used to. -- 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-7753?page=com.atlassian.jira.plugin... ] Dominik Pospisil commented on JBIDE-7753: ----------------------------------------- I have tested this on JBT trunk (JBossAS Tools 2.2.0.v20110114-0319-H78-CR1) and I still see the issue :( -- 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-7753?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-7753: ------------------------------------ hi dominik: i just made a new patch on it. feh. this issue is annoying ;) -- 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-7753?page=com.atlassian.jira.plugin... ] Dominik Pospisil closed JBIDE-7753. ----------------------------------- Verified (jbdevstudio-product-eap-linux-gtk-x86_64-4.0.0.v201101230948R-H100-CR1.jar). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira