[jbossts-issues] [JBoss JIRA] (JBTM-1925) Enable remote debugger in JBossAS/WildFly for all tests

Paul Robinson (JIRA) jira-events at lists.jboss.org
Tue Sep 17 12:04:03 EDT 2013

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

Paul Robinson commented on JBTM-1925:

This now works, however port 8787 is blocked by the firewall on the CI nodes. Therefore, you will need to use port forwarding to access the debug port. Once you have port forwarding setup, it's just a matter of pointing your debugger at localhost:8787.

You can setup port forwarding by running the following command:

ssh -L 8787:localhost:8787 hudson@<CI_NODE_NAME>

Alternatively, you can add the following to your ~/.ssh/config file for each CI node:

        User hudson
        LocalForward 8787 localhost:8787

Then you just need to do this to setup the port forwarding.

> Enable remote debugger in JBossAS/WildFly for all tests
> -------------------------------------------------------
>                 Key: JBTM-1925
>                 URL: https://issues.jboss.org/browse/JBTM-1925
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 4.17.11, 5.0.0.M5
> This allows us to attach to hung AS instances and see what they are doing.
> Adding this to narayana.sh should do the trick:
> {code}
> echo JAVA_OPTS='"$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"' >> ./bin/standalone.conf
> {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

More information about the jbossts-issues mailing list