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

Running process is not terminated after closing in the console #1145

Closed
artaleks9 opened this issue Nov 15, 2016 · 3 comments
Closed

Running process is not terminated after closing in the console #1145

artaleks9 opened this issue Nov 15, 2016 · 3 comments

Comments

@artaleks9
Copy link

artaleks9 commented Nov 15, 2016

When I stop a running process into console by closing tab process, it does not really terminate.

Reproduction Steps:

  • Go to dashboard and create the template 'web-java-petclinic' project from Java-MySql stack.
  • Open the IDE and run the application.
  • Stop application by closing tab process.
  • Perform the command 'ps ax | grep tomcat8' in the terminal.

Expected behavior:

  • Should appear the 'ask-dialog' form.
  • After executing the command in the terminal we can see that process is stopped.

Observed behavior:

  • The 'ask-dialog' form is not appear.
  • After executing the command in the terminal we can see that process is not stopped.

Codenvy version: 5.0.0-M8
OS and version: Ubuntu 14.04

Additional information:
Problem only started happening recently, didn't happen in an older version of Codenvy: Yes
Problem can be reliably reproduced: Yes (sometimes need stop/start application two times that to reproduce this bug).
See the attachment.
stop_process

@dkuleshov
Copy link
Contributor

Hi, seems like the cause of an issue may be related to command output read timeouts. I've spotted the next line in the end of a process console output:

Command output read timeout is reached. Process is still running and has id 531 inside machine

The corresponding code is inside docker plugin: DockerProcess.java#L169-L169

@garagatyi
Copy link
Contributor

From what I see it is possible that problem is in a timeout. Probably API treat process as dead because of timeout and because of that closing console does nothing.

@mshaposhnik
Copy link
Contributor

Is there any reliable way to reproduce this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants