[jboss-jira] [JBoss JIRA] (WFLY-276) Clustering/multi-node tests cannot be run with -Djpda debugger

[Radoslav Husar (JIRA)]

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

Radoslav Husar updated WFLY-276:
--------------------------------

              Summary: Clustering/multi-node tests cannot be run with -Djpda debugger  (was: TS: How to use -Djpda with clustered tests)
    Affects Version/s: 8.0.0.Alpha1


Yep, they both listen on 8787.
                
> Clustering/multi-node tests cannot be run with -Djpda debugger
> --------------------------------------------------------------
>
>                 Key: WFLY-276
>                 URL: https://issues.jboss.org/browse/WFLY-276
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Documentation, Test Suite
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Radoslav Husar
>            Assignee: Ondrej Zizka
>            Priority: Minor
>             Fix For: 8.0.0.CR1
>
>
> The doc now says whats pasted below, but I am not sure if both servers are listening on 8787 because (that would fail the startup), if I have to connect to both or where do I configure that, etc.
> {code}
> Running JBoss AS instances with debugger
> Adding -Djpda (May be changed to -Ddebug in the future) will make JBoss AS run with JPDA JVM arguments for debugging.
> It will suspend and wait for the debugger to connect at port 8787.
> JBoss AS is started by Arquillian, when the first test which requires given instance is run. There's (currently) no challenge text in the console, it will look like the first test is stuck. This is being solved in http://jira.codehaus.org/browse/SUREFIRE-781.
> Depending on which test group(s) you run, multiple instances may be started. In that case, you need to attach the debugger multiple times.
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira