[jboss-jira] [JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner

[Marek Kopecký (JIRA)]

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

Marek Kopecký updated WFCORE-3502:
----------------------------------
    Summary: Fix debug options in test-runner  (was: Test-runner doesn't handle debug options correctly)


> Fix debug options in test-runner
> --------------------------------
>
>                 Key: WFCORE-3502
>                 URL: https://issues.jboss.org/browse/WFCORE-3502
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Marek Kopecký
>            Assignee: Marek Kopecký
>
> Test-runner doesn't handle debug options correctly.
> If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}.
> The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, he uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails:
> {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}}
> {noformat}
> ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
> Error occurred during initialization of VM
> agent library failed to init: jdwp
> Running null
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)