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

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Wed Sep 25 10:14:02 EDT 2013

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

Tom Jenkinson commented on JBTM-1925:

I can't debug from home using the current solution. I think I have the same issue as: http://stackoverflow.com/questions/6717396/eclipse-remote-debugging-a-tomcat-server-behind-a-firewall

In that scenario the solution was to use reverse tunnels.

Am I the only one who can't do the remote debug from outside the office?

/cc [~jhalliday]

> 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