[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-7078) Multiple servers wtih one runtime mismatch

[Rob Stryker (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-7078.
--------------------------------

    Resolution: Cannot Reproduce Bug


I cannot replicate this. I have followed the steps below and deploying to server 2 after starting and publishing to server 1 seems to work fine. I even then alternated, deploying back and forth to both servers and seeing changes pushed to both. 

On an architectural level, it doesn't seem like this would be possible anyway. The only data stored in a runtime object is the location, the vm, and the configuration name, which are only used for the local instance. 

The only way I could see this happening is if server2's behaviour delegate is cached as local before you manage to change the behaviour to RSE via the editor. This, however, would be a different bug which I am still investigating. 

However as listed, I cannot replicate this bug. 

> Multiple servers wtih one runtime mismatch
> ------------------------------------------
>
>                 Key: JBIDE-7078
>                 URL: https://jira.jboss.org/browse/JBIDE-7078
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.M2
>            Reporter: Dominik Pospisil
>            Assignee: Rob Stryker
>
> If I create two servers using single runtime - one local and one remote, starting / stopping / publishing on those servers simultaneously does not work as expected. If I start the local server first, all subsequent operations are attempted to be completed locally and vice-versa.
> Steps to reproduce:
> 1) Create new server rutime (EAP 5.1.CR2)
> 2) Create new local server using created runtime
> 3) Create new remote server using the same runtime
> 4) Start / stop local server
> 5) Start / deploy on remote server

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira