(Java) Remote debugging (and breakpoints) of App server internals

[Stephan van Beerschoten <st...@vanbeerschoten.net>]

Hi there, how would I go about setting breakpoints in server side modules
that are part of my App server? I'm using WildFly, but the same would be
true for any of them I guess.

I can set breakpoints in my own code that work just fine, but I need to get
a breakpoint in the internal apache-cxf engine of my App server to
troubleshoot an issue I have.

Thanks,
Stephan

Re: (Java) Remote debugging (and breakpoints) of App server internals

[Will Hartung <wi...@gmail.com>]

On Fri, Jul 23, 2021 at 4:29 PM Stephan van Beerschoten <
stephan@vanbeerschoten.net> wrote:

> Hi there, how would I go about setting breakpoints in server side modules
> that are part of my App server? I'm using WildFly, but the same would be
> true for any of them I guess.
>
> I can set breakpoints in my own code that work just fine, but I need to
> get a breakpoint in the internal apache-cxf engine of my App server to
> troubleshoot an issue I have.
>

Find the appropriate version of the library your server is using, grab its
source code, and set breakpoints. With Maven, you (might) be able to
download the source attached to the library from the repository. In that
case, you can set breakpoints within that source code.

If you do download the source code, you don't have to worry about any
project structure. You can just create a new project, and drag the source
into it. You don't need to build it, just need to make the IDE aware of it.

The real game is making sure the versions match, that can't take some
digging to find out what version your server is using.

It helps if you can build the server from source, but even that only goes
so far. In your case, WIldfly doesn't build the Apache CXF stuff, it just
imports it. But at least by looking at the server source, you can ideally
ascertain the correct dependency that they're using.

Regards,

Will Hartung