sadebugd and related options in jhsdb have been deprecated by JDK-8338894 since JDK 24, and it would be removed by JDK-8338894.
I'm not going to object about this, but I want to migrate sadebugd to other technology for remote debugging.
sadebugd is very useful for remote debugging. If you want to debug hung process in headless system, sadebugd helps your analysis because jcmd would not work. This case might happen on headless virtual machine or container including Kubernetes especially distroless container.
I've explained the use case on Kubernetes, and have proposed changes to use HTTP for wire protocol for debugging. See following URL for details.
https://mail.openjdk.org/pipermail/serviceability-dev/2025-January/061779.html
I'm not going to object about this, but I want to migrate sadebugd to other technology for remote debugging.
sadebugd is very useful for remote debugging. If you want to debug hung process in headless system, sadebugd helps your analysis because jcmd would not work. This case might happen on headless virtual machine or container including Kubernetes especially distroless container.
I've explained the use case on Kubernetes, and have proposed changes to use HTTP for wire protocol for debugging. See following URL for details.
https://mail.openjdk.org/pipermail/serviceability-dev/2025-January/061779.html
- relates to
-
JDK-8340121 Remove jhsdb debugd and the jhsdb --connect option
-
- Open
-
-
JDK-8338894 Deprecate jhsdb debugd for removal
-
- Resolved
-