microsoft / microsoft/vscode-java-debug

Add/Delete Method not implemented - Hot Code Replace

Open
#1,200 4 comments 2 reactions 1 assignee View on GitHub

@testforstephen is already working on this.

Since Aug 5, 2022.

ai-triaged bug hcr question
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Description

My company works on a larger sized Java project, and we cannot get hot code replace to work in vscode. I suspect this is probably related to something about our specific project and how it's set up, and I'm hoping someone can give further direction for troubleshooting the problem.

Environment
  • Operating System:
    • Host: Ubuntu 22.04/21.10
    • Running App (Docker Images):
      • FROM ghcr.io/graalvm/graalvm-ce:java17-21.3.0
      • FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:18-bullseye (installing graal manually)
  • JDK version: 17 (graal, but also tested using open-jdk)
  • Visual Studio Code version: 1.69.2
  • Java extension version: 1.9.0 (Redhat)
  • Java Debugger extension version: 0.43.0
Steps To Reproduce

Due to the complex nature of our project, I'm not sure how to provide a reproducible example. Here are some things we've tried.

  • We run our java app in a container managed by kubernetes. We are able to attach the debugger to the running process, but hot code deploy will fail to work.
  • We've recently ported our app into a vscode dev container, attached to that local running process, and unsuccessfully done hot code deploy

We came from using NetBeans where this worked flawlessly, and just confirmed it still works. I've also confirmed Intelij can successfully do hot code deploy as well with our project.

Current Result

Our most simple test is adding a system.out to an existing method. No other changes. That produces the following stacktrace.

image

Other Information

We've reviewed the information at here and here with no luck.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.