[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
Wed Jun 22 10:07:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255815#comment-13255815 ]
Rob Stryker commented on JBIDE-21059:
-------------------------------------
I spoke with Fred yesterday discussing some of these issues. I think it might fit better there, but it should also be possible for a user to handle it with a wildfly adapter.
The issues with handling a 'docker' adapter is that the docker must be absolutely generic and extensible. The problem is deploying to a tomcat may just need a .war file deployed, while deploying to wf / eap requires a blah.war AND a blah.war.dodeploy.
Basically, there's custom behavior all over the place that needs to be changeable... so it will require a lot of planning to make something generic enough that can still work for a wide array of usecases. Trying to get some minimal functionality that makes a simple wf docker container work with the existing wildfly server adapter is definitely useful.
Either way, I'd say that this basically works as expected, as a debugger can connect to a simple wf inside a docker container after recent enhancements. The workflow may not be that convenient, but that can be improved through a generic docker container.
> 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.S116
>
>
> 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