[ https://issues.jboss.org/browse/JBIDE-9243?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9243: --------------------------------------- Summary: local servers are not trying to start because it already looks like they are started (was: No console output nor debug process is shown for any servers in M2) Fix Version/s: 3.3.0.M3 (was: 3.3.0.M2) Description: originally: "After I updated to latest M2 build I no longer get console output nor launches - I for sure got that earlier today so something changed. Without console output and way of debugging you are rather lost so this is definitely considered a blocker." After some investigation what actually happend was that I had something running on port 8080 already and then the server didn't even try and start anything and just worked like it was already running... That's different what it used to be that the server would actually start and then most likely start with address already in use; it looked bad but at least the user could see what is going on. The current behavior is worse since the user think he is already running..but turns out he is not. But it is cool the poller now is asked if it is already started and we should use that information to show a dialog to the user asking him something like: "A server already seem to be responding via <some text for the poller to describe what it detected>. Do you wish to continue starting the server, connect to existing server or cancel ?" Then clicking continue will actually do the start, cancel will stop the attempt to start and the server adapter should not be connected and finally connecting to existing server should temporarily for the time of this specific launch switch to "do not start/stop server" mode. Then the user would be in control and know what is going on! was: After I updated to latest M2 build I no longer get console output nor launches - I for sure got that earlier today so something changed. Without console output and way of debugging you are rather lost so this is definitely considered a blocker. -- 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-9243?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9243: ------------------------------------ Steps to Reproduce: 1) start an as7 server 2) start a 2nd as7 server (that would listen on the same port) Result: The adapter of the 2nd server erroneously states "Started" but actually no server was started Symptom is that you have no log output of that 2nd server. -- 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-9243?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9243: ------------------------------- Attachment: JBIDE-9243.png Screenshot of implementation -- 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-9243?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9243: -------------------------------------------- using latest nightly build : 2.3.0.v20110722-1357-H562-M3 I still see this. -- 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-9243?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9243: --------------------------------------- Fix Version/s: 3.3.0.M3 (was: 3.3.0.CR1) Assignee: Jiri Peterka (was: Max Rydahl Andersen) -- 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-9243?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9243: -------------------------------------- I just tried Max' scenario and it worked as suggested by Rob - a dialog appeared offering two options. See here: http://screencast.com/t/y9jMxfVQ -- 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-9243?page=com.atlassian.jira.plugin... ] Len DiMaggio commented on JBIDE-9243: ------------------------------------- I was unable to recreate the error with this build: Version: 2.3.0.v20110817-1456-H644-M3 When I try to start the 2nd server, I see the dialog that is included in this JIRA as a screen shot. Max? -- 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-9243?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9243: -------------------------------------- I just updated my JBT to the latest nightly and have this version of JBossAS Tools: Version: 2.3.0.v20110829-0855-H677-M3 Now I'm getting Max's failure again :( - when I start the second server, it doesn't ask for anything and fails on "ports used". -- 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-9243?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9243: --------------------------------------- Fix Version/s: 3.3.0.M4 (was: 3.3.0.M3) -- 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-9243?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-9243: -------------------------------------- I just checked this on a fresh install of build #24 - M3 candidate. And it works fine. I will ask somebody else to double check. -- 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-9243?page=com.atlassian.jira.plugin... ] Libor Zoubek edited comment on JBIDE-9243 at 9/5/11 7:10 AM: ------------------------------------------------------------- I can confirm sam behaviour as martin. However, I've tried starting 2nd server while the 1st one is in 'Starting' state (you have to be really quick, AS7 startup is very fast). I got both servers started from the tooling point of view, log contained 2nd server startup with errors. I was not able to stop 2nd server - it still says 'Stopping' until big timeout is reached (5mins or so). I know this is an edge or maybe nonsense case, but 'stopping' issue should get fixed. was (Author: lzoubek): I can confirm sam behaviour as martin. However, I've tried starting 2nd server while the 1st one is in 'Starting' state (you have to be really quick, AS7 startup is very fast). I got both servers started from the tooling point of view, log contained 2nd server startup with errors. I was not able to stop 2nd server - it still says 'Stopping' until I restart eclipse. I know this is an edge or maybe nonsense case, but 'stopping' issue should get fixed. -- 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-9243?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9243: ------------------------------- Fix Version/s: 3.3.0.M3 (was: 3.3.0.M4) I've made some small change for m4. Case is as follows: 1) Start as7 server 2) wait until as7 is up. Then start 2nd as7 server 3) use dialog to mark "do not launch; just set to started". 4) wait for as7 server2 up, then stop as7 server 2 5) stuck in stopping mode :( I made a change to the process terminated poller. It was stuck here because the process terminated poller does nothing and assumes that a process terminating will change the server state. The server doesn't change it because it is not set to always not launch, just set to do that THIS time, and did not remember that the most recent start did not launch a new process. So now process terminated poller will at least check if the server has a process and if it is terminated. This does not affect Libor's fast-startup usecase, which still fails, however the 'terminate process' button still fixes that. As of now that's the only answer I have to Libor's use case. The usecase I just mentioned is fixed for m4, Libor's use case is not addressed, but the original issue here has been fixed for m3. -- 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-9243?page=com.atlassian.jira.plugin... ] Len DiMaggio closed JBIDE-9243. ------------------------------- Verified fixed in: jbosstools-3.3_stable_branch.aggregate-Update-2011-09-07_05-39-13-H18.zip A new JIRA will be opened for the related edge case. -- 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-9243?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9243. -------------------------------- Resolution: Done As per isaac, does not require a release note -- 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