ow2-proactive / scheduling-portal Goto Github PK
View Code? Open in Web Editor NEWHome Page: http://try.activeeon.com
License: GNU Affero General Public License v3.0
scheduling-portal's Issues
The getInstance method of the SchedulerServiceImpl class should synchronized
Improve the table updating of the task table and the job info table as it has been done for the job table
When updating the job ouput, the scroll bar is put back to the top which is really not convenient when looking at the end of the logs.
Messages in job detail panel are not always the good ones.
Original issue created by Fabrice Fontenoy on 27, Oct 2010 at 13:01 PM - PORTAL-45
Sometimes it is displayed "No data to display" or "Please select only one job" instead of "waiting for the information..."
Add a java formatter
When a loggin fails, the error message should precise if it is a user/pwd error (authentification error) or a connection error (no REST service for instance)
When updating the job output, the message is totally removed while waiting for the server response. The logs should not be removed during this waiting time.
bind refresh buttons on account and statitic view
do not log an empty message when no job filter is set
Kill job is not functional
Original issue created by Christian Delbé on 05, Jan 2011 at 13:31 PM - PORTAL-62
When killing a running job (164) :
Wed Jan 05 13:31:16 GMT+100 2011 (link: core.client.presenter, WARNING): Submitting job. Trying to submit the file job.xml to the Scheduler.
Wed Jan 05 13:31:17 GMT+100 2011 (link: core.client.presenter, WARNING): Job submitted. A new job with the id 164 having the name: Generated Job was submitted.
Wed Jan 05 13:31:29 GMT+100 2011 (link: core.client.presenter, WARNING): Killing job. Trying to kill the job 164.
Wed Jan 05 13:31:29 GMT+100 2011 (link: core.client.presenter, WARNING): The job having the id 164 could not be killed.
Wed Jan 05 13:31:29 GMT+100 2011 (link: core.client.presenter, WARNING): The error message: "404 - Not Found error. <title>Apache Tomcat/6.0.26 - Error report</title><style></style>
HTTP Status 404 - Could not find resource for relative : /scheduler/jobs/164/kill of full path: http://localhost:8080/proactive_grid_cloud_portal/scheduler/jobs/164/kill
type Status report
message Could not find resource for relative : /scheduler/jobs/164/kill of full path: http://localhost:8080/proactive_grid_cloud_portal/scheduler/jobs/164/kill
description The requested resource (Could not find resource for relative : /scheduler/jobs/164/kill of full path: http://localhost:8080/proactive_grid_cloud_portal/scheduler/jobs/164/kill) is not available.
Apache Tomcat/6.0.26
" occurred when trying to kill the jobs with the id 164.Scheduler Portal is not Java 5 Compliant due to some String.isEmpty() invocation
When refreshing the page, we've got a NPE when trying to access a properties
gwt-log.jar in RM portal is referenced with absolute path in eclipse config file (should be relative)
When requesting task list, job info or job output of a finished/canceled job, information should be saved and requests to the server should be performed anymore.
prevent refresh of the jobs list when a refresh is already running
RM Portal: When classes have been copied from Scheduler portal to RM portal, comments and javadoc have not been updated. Still many references to "scheduler".
when trying to get the job output of a canceled job, SchedulerServiceImpl.getJobOuput() raises a NullPointerException
Original issue created by Fabrice Fontenoy on 20, Oct 2010 at 18:10 PM - PORTAL-35
This is due to typo in DefaultLoggers:
Instead of SERVER(Loggers.PRESENTER, Loggers.DEFAULT_LEVEL), we should have SERVER(Loggers.SERVER, Loggers.DEFAULT_LEVEL)
When we disconnect a user, the synchronization process on server side raised a exception
Original issue created by Fabrice Fontenoy on 19, Oct 2010 at 18:12 PM - PORTAL-32
That spawns the end of the server side synchronized and thus, when another (or the same) tries to connect afterwards, he doesn't get the new job updates.
Exception messages refer to the name of the rest.url property instead of its value. Exception message has not been changed after the refactoring of properties.
set refresh rate to 5 seconds by default
Once a job finished, it is no longer necessary to refresh task list, job info and job output.
When a user selects a job in the job list and then sorts the job table, then the selection is removed. A way to keep this selected should be found.
client side : do not fetch jobs continuously but only when the state has changed
JobInfo view is not so beautiful, it could be better to apply a left (instead of center) align on each column
ScrollPanel height in the log panel should be defined in percentage and not in pixels
The log timer for the footer bar would be set on the presenter side instead of the view side
The project should be 1.5 compliant
Original issue created by Hagea Anemona Oana on 16, Aug 2010 at 17:24 PM - PORTAL-1
Some override annotations are not 1.5 compliant.
Disconnection does not work properly
Original issue created by Fabrice Fontenoy on 26, Oct 2010 at 18:00 PM - PORTAL-44
When you disconnect and reconnect right atfer, it is not possible to get some details (tasks, job info and logs) on a job anymore.
The application says that you are not connected and ask you to get connected first
SynchronizationTimerTask remains active even when all clients are deconnected
Original issue created by Arnaud Contes on 30, Dec 2010 at 17:41 PM - PORTAL-58
not found a scheduler frontend for sessionId 4
status: Unauthorized
org.ow2.proactive_grid_cloud_portal.shared.exception.JobSynchronizationException: Exception occured while trying to synchronize the job list with the scheduler throught the REST service located at http://localhost:8080/proactive_grid_cloud_portal
at org.ow2.proactive_grid_cloud_portal.server.SchedulerServiceImpl$SynchronizationTimerTask.run(SchedulerServiceImpl.java:1168)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
After a user clicks on "Connect" and before the result appears, a "waiting..." or "loading..." message should be displayed to inform the user that the resquest is processing
Excetion constructors with a message argument don't use this message.
The levels of the client-side loggers cannot be set.
Original issue created by Hagea Anemona Oana on 09, Sep 2010 at 11:35 AM - PORTAL-11
The default value of the client-side loggers cannot be changed.
RM Portal: the name of the window is still "ProActive Scheduler". Should be ProActive Resource Manager
documentation target doc-jaxrs does not work
Original issue created by Arnaud Contes on 02, Nov 2010 at 10:04 AM - PORTAL-48
10:02:08{master proactive_grid_cloud_portal.git} % ant doc-jaxrs
Buildfile: build.xml
doc-jaxb:
BUILD FAILED
/home/acontes/ws_git/proactive_grid_cloud_portal.git/build.xml:75: No source files and no packages have been specified.
Total time: 1 second
(link: 1) 2168 exit 1 ant doc-jaxrs
From time to time, JobDetailsPresenterImpl.onFailure raised a ClassCastException
Original issue created by Fabrice Fontenoy on 20, Oct 2010 at 17:21 PM - PORTAL-34
java.lang.ClassCastException: com.google.gwt.user.client.rpc.StatusCodeException cannot be cast to org.ow2.proactive_grid_cloud_portal.shared.exception.RestServerException
at org.ow2.proactive_grid_cloud_portal.client.presenter.scheduler.visualization.job.JobDetailsPresenterImpl$2.onFailure(JobDetailsPresenterImpl.java:127)
at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:218)
at com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:287)
at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:393)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
...
Properties are not set on client side
RM Portal: Servlet url of the Resource Manager Service is "proactivegridcloudportal/scheduler" in web.xml file. Should be "proactivegridcloudportal/rm"
When the user logs out, the cooky storing his session id should be removed.
Add the functionality to detach the log panel
properties in config.properties and logger levels in logger.properties should be commented
Original issue created by Fabrice Fontenoy on 20, Oct 2010 at 11:02 AM - PORTAL-33
The default values are written in DefaultProperties and DefaultLoggers.
config.properties and logger.properties should not define another default behaviour, so there is no need to override properties if values are the same.
remove the state refresh feature
Original issue created by Arnaud Contes on 06, Jan 2011 at 09:19 AM - PORTAL-64
this does not work correctly leading to messages like 'you are not connected ...'
The same process already exists in the rest part ans works fine.
jobinfo : send json instead of reificating the result into objects
Original issue created by Arnaud Contes on 13, Jan 2011 at 09:52 AM - PORTAL-73
we spend too much time recontructing the array of reified object in the server part of GWT, then sending it to the client. We should consider forwarding the json result to the client and let it do what it wants with the json.
several methods in SchedulerServiceImpl do not check the reponse status and fails in the status code is different from 200
ensure that a click on the disconnect button logs off the user
Change log panel style. The current one is ugly
apply the same css style on logs, account,statitic views
A rest client should be created for every call to the rest service.
Original issue created by Fabrice Fontenoy on 22, Oct 2010 at 18:00 PM - PORTAL-37
If we have only one client for all the requests, we are compeled to synchonize its usage which is bad for the application performance.
Add Licence header for every java file
RM ui is not java 5 compliant due to some @Override annotations
After a disconnection, presenters of the previous sessions are still alive and they are still handling events.
Original issue created by Fabrice Fontenoy on 27, Oct 2010 at 14:41 PM - PORTAL-46
This implies that every event are handled as many time as we have been connected.
This implies also that they are many failed request since they are using previous session id no longer valid.
We can consider 2 solutions for this issues:
- Use a singleton pattern for presenters. Presenters are translated into Javascript so the behaviour of this pattern should be tested first but it seams that the singleton pattern is only valid for one tab. That implies that we will have 2 instances on 2 tabs but only one instance on one tab. This is the behaviour that we aim at providing (at most one session per tab but we can have several sessions using several tabs).
When a reconnection is performed, we can just change the sessionId of the main presenter (SchedulerPresenter) and this presenter will propagate this modification to its sub-presenter and so on and so forth. One thing we have to take care of, is the initialisation of displays (should be called by its presenter). Otherwise, next user we be able to the last screen of the previous user. - Make every presenter handle the LogoutEvent in which we can call a doLogout() method for example that will perform operations necessary to remove all references and thus will make the GC possible. Remember that a presenter has a reference towards its view (Display) which itself has a reference towards its presenter. So the presenter has to call a method on its display to remove the reference towards itself and then it has to remove reference towards its display.
There is maybe a better and/or shorter solution but using one of these two solutions should fix this issue.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.