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

Can't connect to Che server with debug session #3367

Closed
vparfonov opened this issue Dec 13, 2016 · 5 comments · Fixed by #3371
Closed

Can't connect to Che server with debug session #3367

vparfonov opened this issue Dec 13, 2016 · 5 comments · Fixed by #3371
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@vparfonov
Copy link
Contributor

Following this docs Che server should be available for debugging it torn on DevMode but this is not work.

Reproduction Steps:

  1. Start Che with this command:
    docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /home/vetal/che:/data -v /home/vetal/codenvy/projects/che:/repo eclipse/che-cli:nightly start
  2. Try to connect debug session to the host: 172.17.0.1 port: 8000
    Expected behavior:
    Debug session should be connected
    Observed behavior:
    Error running Unnamed: Unable to open debugger port (172.17.0.1:8000): java.net.ConnectException "Connection refused"

Che version: 5.0.0-M9-SNAPSHOT
OS and version: Ubuntu 16.04
Docker version: 1.12.3
Che install: Docker container

Additional information:

cli.log

@vparfonov vparfonov added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Dec 13, 2016
@vparfonov vparfonov added this to the 5.0.0-M9 milestone Dec 13, 2016
@riuvshin riuvshin self-assigned this Dec 13, 2016
@riuvshin riuvshin added team/production sprint/current status/in-progress This issue has been taken by an engineer and is under active development. labels Dec 13, 2016
@riuvshin
Copy link
Contributor

I did investigation on that and it seems i've found the issue.
https://github.com/eclipse/che/blob/master/dockerfiles/che/entrypoint.sh#L159 this is never true even in dev mode that is why jpda is not work

locally I did same way as in codenvy https://github.com/codenvy/codenvy/blob/master/dockerfiles/codenvy/entrypoint.sh#L44 here we always use ${JPDA} and it will be set only in dev mode in env file. so in prod mode it will be just empty.

I can issue PR with my changes but Im not sure it is a good solution for CHE so @benoitf @TylerJewell I need your help here I don;t know how to fix that CHE_DEBUG_SERVER
it is expected that it will be automatically set to true if dev mode is ON. After refactorings I don't understand how it works now and where fix should be.

@TylerJewell
Copy link

Let's solve this immediately after roadmap call.

benoitf added a commit that referenced this issue Dec 13, 2016
…a mode)

Fix #3367

Change-Id: I1de413e1e7b5fce4631055811b2b2b879b3052aa
Signed-off-by: Florent BENOIT <[email protected]>
@benoitf
Copy link
Contributor

benoitf commented Dec 13, 2016

I've submitted fix #3371

for now as eclipse/che-server image is also used by the launcher we had to use the same setting (CHE_DEBUG_SERVER)

@benoitf benoitf added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Dec 13, 2016
benoitf added a commit that referenced this issue Dec 13, 2016
…a mode) (#3371)

Fix #3367

Change-Id: I1de413e1e7b5fce4631055811b2b2b879b3052aa
Signed-off-by: Florent BENOIT <[email protected]>
@benoitf benoitf removed sprint/current status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Dec 13, 2016
@benoitf
Copy link
Contributor

benoitf commented Dec 13, 2016

@vparfonov please test with pulling again the cli image
@vparfonov and reopen issue if it's still not working for you

@vparfonov
Copy link
Contributor Author

Confirm works for now

@bmicklea bmicklea mentioned this issue Jan 13, 2017
70 tasks
JPinkney pushed a commit to JPinkney/che that referenced this issue Aug 17, 2017
…a mode) (eclipse-che#3371)

Fix eclipse-che#3367

Change-Id: I1de413e1e7b5fce4631055811b2b2b879b3052aa
Signed-off-by: Florent BENOIT <[email protected]>
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. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants