Restart stop but not start the program

[llgcode]

Restart doesn't work, when hit restart button the process terminate but not restart.

Environment

• Operating System: win10
• JDK version: jdk1.8.0_112
• Visual Studio Code version: 1.41.1
• Java extension Pack version : 0.8.1
• Java Debugger extension version: 0.24.0 - 2019-12-25

Current Result

Stop the program

Expected Result

Rerstart the program

[akaroml]

@llgcode thanks for reaching out.

It would be very helpful if you could share a sample project with us. Even a very simplified version will help. Would you please provide that?

[llgcode]

hi @akaroml,
I can't provide you my project, I've tried to create a sample project but can't reproduce the issue.
I found in Language Suport for Java output this warning when relaunching the program:

[Warn - 10:58:50 AM] Feb 12, 2020 10:58:50 AM Failed to destory launch files, will retry again.

[llgcode]

I've reproduced the issue :-) in the sample project ! by setting this setting in launch.json

...
"shortenCommandLine": "jarmanifest",
...

Please found the sample project here:
java-ws-1.zip

[testforstephen]

i can reproduce it with the sample project. thanks for reporting.

[testforstephen]

this looks like an issue in the upstream, see microsoft/vscode#87767 (comment).

[testforstephen]

The java debugger adds some step to clean up the temp files during handling the disconnect request. And considering the temp files may be occupied by the debuggee process, so the debug will retry 5 times for cleaning the temp files, the sleep interval for each retry is 1s.

On the other hand, vscode uses the 500ms timeout for disconnect request, see microsoft/vscode#87767 (comment). That means if the disconnect request handler in the debugger didn't return the response in 500ms, the debug session will shutdown instead of restart.

I've reproduced the issue :-) in the sample project ! by setting this setting in launch.json
...
"shortenCommandLine": "jarmanifest",
...

Failed to destory launch files, will retry again.

The user used jarmanifest option, the debugger will need clean up the temp manifest jar during disconnect request. From the log file, the debugger retried one more time to clean up the temp file, that means the debugger returned the response in at least 1s. This is beyond of the vscode limit.

The fix is to change the retry interval from 1s to 100ms, this will make the debugger to return the response in 500ms.

[llgcode]

I hope it will work in my case.
Thanks for your support.