I am not hopeful for this to make 3.3.0 at all, but, for now I am targeting to RC1 just in case. THe launching code is currently being unified by Andre and so adding something such as this is not feasible until his unification is complete.

Screenshot of implementation

Implemented as in the screenshot attached =] Text can be changed if it's deemed that it's necessary.

reopening since this does not seem to work.

Creates one AS 7 server, start it, verify that it runs.
Copy AS 7 server adapter, start it, expect warning dialog comes up.

For me both servers start - without warning

I am not able to replicate this. Just tried, and the 2nd attempt to start a 7.0 brings up the dialog. Whether I start the first one from cmd line or from within eclipse, the second attempt always brings up the dialog for me.

Are you still able to replicate this?

using latest nightly build : 2.3.0.v20110722-1357-H562-M3

I still see this.

Assigning to you to really double check.

Maybe we should have QE give it a try, too?

Jiri - can you or someone from you team take a look ?

here is one of my failed attempts
http://screencast.com/t/veVkwUzN3Dh

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

I used a slightly newer build than Max:

jbosstools-3.3_trunk.aggregate-Update-2011-08-17_04-18-17-H3519.zip

JBossAS Tools
Version: 2.3.0.v20110816-2052-H641-M3

You may try that, Max, or else I don't know

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?

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".

I will try again on Wed with the M3 build.

Moving past M3 - martin, got any update?

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.

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.

Assigning back to Rob for him to comment.

I'm marking this as complete. I recognize Libor's edge case, however, a failproof way to stop the second server is to check the "Console" view and terminate the process.

I really think that's about all we can do here.

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.

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.

reopening to set release note information

This issue was never seen by a customer so it does not require a release note.

As per isaac, does not require a release note

Closing again.