Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPE in DisconnectRequestHandler.destroyDebugSession(DisconnectRequestHandler.java:28) #13967

Closed
5 of 23 tasks
apupier opened this issue Jul 23, 2019 · 6 comments
Closed
5 of 23 tasks
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@apupier
Copy link
Contributor

apupier commented Jul 23, 2019

Describe the bug

I have an NPE in Language Support for Java Output log

Che version

  • latest
  • nightly
  • other: please specify

Che-Theia@4ef1d89 using Theia@4ef1d89

Steps to reproduce

don't know
was playing with a Springboot app, clicking Debug from the Application.java main method

Expected behavior

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

image

Installation method

  • chectl with -a operator
  • che-operator
  • minishift-addon
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

Additional context

[Error - 9:34:31 AM] Jul 23, 2019 9:34:31 AM [error response][disconnect]: java.lang.NullPointerException
null
java.lang.NullPointerException
	at com.microsoft.java.debug.core.adapter.handler.DisconnectRequestHandler.destroyDebugSession(DisconnectRequestHandler.java:28)
	at com.microsoft.java.debug.core.adapter.handler.AbstractDisconnectRequestHandler.handle(AbstractDisconnectRequestHandler.java:42)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.lambda$dispatchRequest$0(DebugAdapter.java:85)
	at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981)
	at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.dispatchRequest(DebugAdapter.java:84)
	at com.microsoft.java.debug.core.adapter.ProtocolServer.dispatchRequest(ProtocolServer.java:118)
	at com.microsoft.java.debug.core.protocol.AbstractProtocolServer.lambda$new$0(AbstractProtocolServer.java:78)
	at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:60)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(ObservableObserveOn.java:200)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(ObservableObserveOn.java:252)
	at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:61)
	at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:52)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[Error - 9:36:33 AM] Jul 23, 2019 9:36:33 AM [error response][disconnect]: java.lang.NullPointerException
null
java.lang.NullPointerException
	at com.microsoft.java.debug.core.adapter.handler.DisconnectRequestHandler.destroyDebugSession(DisconnectRequestHandler.java:28)
	at com.microsoft.java.debug.core.adapter.handler.AbstractDisconnectRequestHandler.handle(AbstractDisconnectRequestHandler.java:42)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.lambda$dispatchRequest$0(DebugAdapter.java:85)
	at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981)
	at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.dispatchRequest(DebugAdapter.java:84)
	at com.microsoft.java.debug.core.adapter.ProtocolServer.dispatchRequest(ProtocolServer.java:118)
	at com.microsoft.java.debug.core.protocol.AbstractProtocolServer.lambda$new$0(AbstractProtocolServer.java:78)
	at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:60)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(ObservableObserveOn.java:200)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(ObservableObserveOn.java:252)
	at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:61)
	at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:52)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[Error - 9:37:35 AM] Error: The command 'editor.action.formatSelection' cannot be executed. There are no active handlers available for the command.
[Error - 9:38:02 AM] Jul 23, 2019 9:38:02 AM [error response][disconnect]: java.lang.NullPointerException
null
java.lang.NullPointerException
	at com.microsoft.java.debug.core.adapter.handler.DisconnectRequestHandler.destroyDebugSession(DisconnectRequestHandler.java:28)
	at com.microsoft.java.debug.core.adapter.handler.AbstractDisconnectRequestHandler.handle(AbstractDisconnectRequestHandler.java:42)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.lambda$dispatchRequest$0(DebugAdapter.java:85)
	at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981)
	at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124)
	at com.microsoft.java.debug.core.adapter.DebugAdapter.dispatchRequest(DebugAdapter.java:84)
	at com.microsoft.java.debug.core.adapter.ProtocolServer.dispatchRequest(ProtocolServer.java:118)
	at com.microsoft.java.debug.core.protocol.AbstractProtocolServer.lambda$new$0(AbstractProtocolServer.java:78)
	at io.reactivex.internal.observers.LambdaObserver.onNext(LambdaObserver.java:60)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(ObservableObserveOn.java:200)
	at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(ObservableObserveOn.java:252)
	at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:61)
	at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:52)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
@apupier apupier added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 23, 2019
@apupier
Copy link
Contributor Author

apupier commented Jul 23, 2019

I think that it happens when clicking on the red square to stop debug inside the Debug View

@nickboldt
Copy link
Contributor

Does this prevent you from doing anything, or is it just log clutter that should be cleaned up (error should be caught better) ?

@nickboldt nickboldt added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 24, 2019
@slemeur
Copy link
Contributor

slemeur commented Jul 24, 2019

@tsmaeder : this lands into your team backlog, as something to try to reproduce.
As the steps to reproduce the issue are unclear -> backlog of 7.x

@slemeur slemeur added this to the 7.x milestone Jul 24, 2019
@slemeur slemeur added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 24, 2019
@apupier
Copy link
Contributor Author

apupier commented Jul 25, 2019

Does this prevent you from doing anything, or is it just log clutter that should be cleaned up (error should be caught better) ?

I detected no functional problem. I would say that it is jug log clutter that should be cleaned up.

@tsmaeder tsmaeder mentioned this issue Sep 10, 2019
41 tasks
@tsmaeder
Copy link
Contributor

Need to analyze whether this is something that may happen (because timeout or something similar). If yes, write out a reasonable log message that makes clear this is nothing to worry about. If this is a problem, fix it or if too complicate defer for later implementation

@tsmaeder tsmaeder modified the milestones: 7.x, Backlog - Languages Sep 23, 2019
@tsmaeder tsmaeder mentioned this issue Sep 24, 2019
30 tasks
@tsmaeder tsmaeder removed this from the Backlog - Languages milestone Sep 25, 2019
@tsmaeder tsmaeder mentioned this issue Oct 11, 2019
26 tasks
@che-bot
Copy link
Contributor

che-bot commented Mar 25, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 25, 2020
@che-bot che-bot closed this as completed Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

5 participants