]
Max Rydahl Andersen commented on JBIDE-21059:
---------------------------------------------
Also, this is probably not limited to docker - it is probably for any remote/externally
managede server adapter.
There should be two things fixed:
A) if Debug mode can't actually connect a debugger the server adapter should not go
into debugging mode - it should tell the user it cannot connect.
B) the server adapter should have or ask enough info to setup a remote debugging launch -
just like it does if it started the server it self.
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.