Page History

Fabio, Anders, Max, and Steve:

I was following up with Fabio's report, and was having great success selecting and updating runs, and viewing the plots. The monitoring front end was very responsive.

Then Anders had a problem with the OpsLog. So I opened the OpsLog (I didn't even have the application opened in my browser previously) and logged in.

Then I returned to the monitoring application, tried to update a single run and it took a couple minutes, re-selected ALL the runs and "timed me out" of the ops log with this message (which I received only after trying to force authentication-checking by creating a new entry):

<quote>
Your session has timed out.

If there is no activity from the browser in 3 hours the server releases the session. We limit the length of the session to control the load on the server. The server has no way of telling whether the browser is still connected other than to monitor its activity. If the sessions are too long the server keeps abandoned session open for an infinite time. They accumulate quickly and consume the memory.

Please return to the index and log in again.
</quote>

I'm going to hazard a guess that there's something conflicting between Max's and Steve's sessions, but I can't be sure as I'm not an expert web-developer.

For the moment, perhaps you can work around this by using one browser for the OpsLog and another for the monitoring/trending applications? I will notify Max and Steve by email, and copy my notes into the OpsLog (once I log in again) so they can follow up tomorrow morning.

If the problem is so severe that it can't wait until morning I can start waking people up. Let me know.

-Dan

And at the same time I got looged out of Ops Log.

anders

On Thu, 26 Jun 2008, Anders Borgland wrote:

>
> I tried to look at the quantity SGPSBA_CURRDOP and got:
>
> java.lang.NullPointerException
> org.freehep.webutil.tree.TreeUtils.nodesForPath(TreeUtils.java:17)
>
> org.glast.base.application.web.filter.ApplicationFilter.defaultApplica
> tionFilter(ApplicationFilter.java:248)
>
> org.glast.base.application.web.filter.ApplicationFilter.doFilter(Appli
> cationFilter.java:173)
>
> org.glast.base.web.multipart.filter.MultipartFilter.doFilter(Multipart
> Filter.java:37)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilte
> r.java:118)
>
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter
> .java:52)
>
> org.glast.base.web.datasource.DataSourceFilter.doFilter(DataSourceFilt
> er.java:119)
>
> org.glast.base.web.groupchecker.filter.GroupCheckerFilter.doFilter(Gro
> upCheckerFilter.java:43)
>
> org.glast.base.web.login.filter.LoginFilter.doFilter(LoginFilter.java:
> 127)
>
> org.glast.base.web.checkcookies.filter.CheckCookiesFilter.doFilter(Che
> ckCookiesFilter.java:41)
>
>
> Seems to happen to all quantities.
>
> anders

During my last two shifts (177C and 178C) sometimes I have had a problem with the Data Quality Monitoring In the DataQualityMonitoring page http://glast-ground.slac.stanford.edu/DataQualityMonitoring/^{Image Removed}
i don't manage to check only one run in the run table. Every time i check only one and then click on the "update" button, it takes a while "thinking" and at the end all the run are checked again If I instead click directly to the data products link (digi, recon, etc )of the run I'm interested in, i go the the data monitoring page but i cannot see any plot.
I have also noticed that when this happen I'm automatically logged off from the opslog Do you have suggestions?