[jbosstools-issues] [JBoss JIRA] (JBIDE-10756) Debug button attempts to start already running server, reports port in use

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-10756:
-------------------------------------

Hi James:

The screenshots you are showing indicate you are using generic server adapters, the jboss server adapters bundled with eclipse and wtp. We can tell this because the server editor (2nd pic) is pretty empty compared to ours, and the error dialog (first pic) is not something we put up. These are definitely generic servers. 

I've tested this issue using jboss tools in a new workspace with jboss-tools only server adapters, and the only way i've been able to replicate anything remotely similar is when you previously ran an app (dynwebProject1) on one server (server1), then stopped it, then started server 2, then reran your "run on server" action from the debug menu pull down, which immediately attempts to launch server1 again. 

In JBossTools, though, a dialog is thrown up indicating another server is found running, and would we like to set the new server adapter to 'running' without launching a new instance, cancel the launch, or launch a new instance anyway.  This dialog is not showing up in your screenshots.

Either way, I can honestly assure you that you are using the generic server adapters and not the jbosstools adapters.  In the new server wizard, directly above "JBoss Community", is another category "JBoss". I believe that you have been using these adapters. 

You can verify this if you want.  In the servers view, right click on your server, then select "properties". In the "general" tab you will see a button "Switch Location".  Press it. You will see a new project appear in your workspace, "servers", inside which you will see a file named JBoss 4.2.server.   Right-click that file, open in -> text editor. You will almost 100% see the following somewhere in that file:

server-type-id="org.eclipse.jst.server.generic.jboss42"

Good luck!
                
> Debug button attempts to start already running server, reports port in use
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-10756
>                 URL: https://issues.jboss.org/browse/JBIDE-10756
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>         Environment: Indigo (Win XP)
>            Reporter: James Wilson
>            Assignee: Rob Stryker
>            Priority: Optional
>         Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
>
>
> I've added a JBoss AS (4.2) server to the Servers view. I select it and then press the "Start the server in debug mode" button on the Servers view toolbar. When I want to run my application I usually click on the Debug button on the main Eclipse toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools 3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at localhost (already running)", and if I click on it I get a message box stating:
> 'Launching JBoss v4.2 at localhost' has encountered a problem.
> Server port In Ue 80080-Http
> In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again and it all works fine after that.

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