[jbosstools-issues] [JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
Rob Stryker (JIRA)
issues at jboss.org
Thu Nov 5 20:47:00 EST 2015
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126223#comment-13126223 ]
Rob Stryker commented on JBIDE-21059:
-------------------------------------
This issue is related to remote debugging not be present for any remote server. I'd suggest there's a slight difference in scope though.
I would guess the linked issue is for when launching a remote server in debug mode, to also set up a remote debugger.
I'd imagine this one is for externally-launched app servers (since we don't currently launch wildfly instances that are inside docker, do we?)
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list