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

Dashboard failed to load when there is a bad scheduler service is saved #4

Closed
GoogleCodeExporter opened this issue Mar 18, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

When saving a RMI client scheduler config, this could lead to scheduler load 
failure if RMI server is down. And the dashboard shows error because of this.

Original issue reported on code.google.com by saltnlight5 on 9 Sep 2011 at 2:37

@GoogleCodeExporter
Copy link
Author

This is fixed in a way that webapp will not let you create the RMI Client 
scheduler config if server is not up. 

We should really let the creation to proceed and just not start the scheduler.

Original comment by saltnlight5 on 9 Sep 2011 at 5:22

@GoogleCodeExporter
Copy link
Author

Fixed. As part of the backend reworked, it now load everything by a configId, 
which handle the error scenerio better when scheduler is not initialized, like 
RMI Client/Server conn problem.

Original comment by saltnlight5 on 12 Sep 2011 at 4:52

  • Added labels: 2.1.0

@GoogleCodeExporter
Copy link
Author

Original comment by saltnlight5 on 12 Sep 2011 at 4:53

  • Changed state: Fixed

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

1 participant