You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
When I stop a running process into console by closing tab process, it does not really terminate.
Reproduction Steps:
Expected behavior:
Observed behavior:
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.
The text was updated successfully, but these errors were encountered: