[
https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-21059:
---------------------------------------
Hello [~rob.stryker],
First, you'll need to build an image of WildFly that has support for remote debugging.
Here's what you should put in a {{Dockerfile}}:
{code}
FROM jboss/wildfly:10.0.0.Final
MAINTAINER Rob
# # expose debug and mgmt ports
EXPOSE 8787
EXPOSE 9990
# start WildFly in standalone/debug mode and allow management from host
CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c",
"standalone.xml", "-b", "0.0.0.0", "-bmanagement",
"0.0.0.0" , "--debug"]
{code}
Then buid you image using the following command:
{code}
docker build -t rob/wildfly-debug:10.0.0.Final .
{code}
And finally you can run the image
{code}
docker run --name wildfly-debug -p 8787:8787 -p 8080 rob/wildfly-debug:10.0.0.Final
{code}
Then you'll have a container named {{wildfly-debug}} running on your Docker VM, and
from there you can connect a remote debugger on port
{{<docker_vm_IP_address>:8787}}
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)