[jboss-jira] [JBoss JIRA] Updated: (JBAS-7582) Stop jbm-cluster2 server

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-7582:
-----------------------------------

    Fix Version/s: JBossAS-6.0.0.M3
                       (was: JBossAS-6.0.0.M2)


Moving to M3 as I highly doubt we'd put another JBASM release in to get JBASM-35. And yeah, Clebert, I expect this will just end up resolved as out-of-date. Only reason it would get fixed is because it's trivial once JBASM-35 is done, and JBASM-33 and 35 are good general improvements to that library.

> Stop jbm-cluster2 server
> ------------------------
>
>                 Key: JBAS-7582
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7582
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M3
>
>
> The tests-jbossmessaging-cluster testsuite target doesn't stop one of the two AS instances it starts. One of the tests stops the server and the ant target assumes that will happen so it doesn't do it.  This is fragile since problems with the test can prevent the server being stopped. That server remaining alive then screws up the rest of the testsuite run. This is a frequent cause of hudson testsuite failures.
> We need to find a way to have ant stop this server if the test didn't.

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