[jbosstools-issues] [JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
Martin Malina (JIRA)
issues at jboss.org
Wed Jul 27 08:23:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271287#comment-13271287 ]
Martin Malina commented on JBIDE-21059:
---------------------------------------
[~rob.stryker], I need some clarification here.
Do I read it right that nothing was done here? Attaching a remote debugger to rse servers was done as part of other JIRA(s) recently. So as a result, this somewhat works, right?
But I have a hard time starting the server adapter in debugging mode. You say that management poller will fail because there no credentials set up. So I need to wait for the timeout? Because I waited several minutes and it was still "Starting". Then I stopped it, changed to web pollers which should work - the homepage at 10.1.2.2:8080 is working fine for me - and again, it's stuck on "Starting". Any suggestions?
> 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
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM1
>
>
> 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