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.

Sign up for GitHub

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

Jump to bottom

Ws-agent has stopped in some case #1817

Closed
vparfonov opened this issue Jul 18, 2016 · 3 comments
Closed

Ws-agent has stopped in some case #1817

vparfonov opened this issue Jul 18, 2016 · 3 comments
Assignees
@svor @vparfonov
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@vparfonov
Copy link
Contributor

Steps to reproduce:

  1. Import Che-project
  2. Wait till resolving project
  3. Open a java class
  4. Run 'Maven/Reimport'
  5. Open another java class
    Actual result: ws-agent has stopped
    ws_agent_error
@vparfonov vparfonov added kind/bug Outline of a bug - must adhere to the bug report template. sprint/next team/ide labels Jul 18, 2016
@vparfonov vparfonov added this to the 4.6.0 milestone Jul 18, 2016
@bmicklea bmicklea added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Jul 26, 2016
@bmicklea
Copy link

The client should check the status of ws-agent and print out a helpful message to let the user know that the memory has run out. Suggest that they add more memory to Che and try again.

Had been filed as CHE-14

@bmicklea bmicklea mentioned this issue Jul 26, 2016
Closed
64 tasks
@riuvshin riuvshin mentioned this issue Jul 28, 2016
Closed
@riuvshin
Copy link
Contributor

This issue actual only with disabled swap for docker containers. On nightly we disabled swap to be able to reproduce and work on those issues, when ws agent is dead we should explain user what was happened, why and what to do.
So to summarize it is not actually blocker because we will keep beta with enabled swap until we will properly manage that failure.
@bmicklea @TylerJewell @vparfonov WDYT?

@riuvshin riuvshin removed the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Jul 28, 2016
@riuvshin riuvshin assigned vparfonov and unassigned svor Jul 28, 2016
@riuvshin riuvshin mentioned this issue Jul 29, 2016
Closed
@bmicklea bmicklea removed this from the 4.6.0 milestone Jul 29, 2016
@vparfonov vparfonov added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Aug 2, 2016
@vparfonov vparfonov removed the status/in-progress This issue has been taken by an engineer and is under active development. label Aug 15, 2016
@vparfonov
Copy link
Contributor Author

Workaround #2369

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svor svor

@vparfonov vparfonov

Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@svor @vparfonov @riuvshin @bmicklea