Ian,
The full stack trace is attached to this message.
I'd tried changing the url reference to "/coregui" and "/coregui/"
but
unfortunally the error persisted.
So it's 60 minutes the session expire time... Since the session will be
open for a read only user this might not be a so severe security problem. I
suppose that is not possible to change the timeout for only one user right
now but it is for the whole system? It might be an option for us.
Your suggestions are appreciated.
Thank you.
2012/2/15 Ian Springer <ian.springer(a)redhat.com>
Can you copy and paste the full stack trace of the Globally Uncaught
Exception into this thread? A lot of it got cut off on the right in the
screenshot you attached.
I think the issue might be here that we reset the GUI's session expiration
timer any time we detect the user navigating to a new "view" within the app
(views are designated by the #XXX portion of the URL). Doing a hard browser
refresh where the #XXX does not change might not count as a user navigation
and therefore not trigger a reset of the session timer. One thing you could
try is changing the URL of your iframe from <
http://rhq:7080/coregui/#Dashboards>
http://rhq:7080/coregui/#Dashboards
to
http://rhq:7080/coregui/ <
http://rhq:7080/coregui/#Dashboards>. This
might work because, you're switching from the view "Dashboards" to the
view "". And "" will "redirect" to "Dashboards"
anyway, so your console
would still work as desired. This is all theoretical though. Let me know if
you have any luck. If not, I may have some other ideas.
I would file a BZ for a new feature that allows an RHQ admin user to
disable the 60 min session timeout for a particular session after logging
in. Obviously, disabling the timeout could be seen as a security risk, so
we could display a confirmation dialog, e.g. "Are you sure you want to
disable session timeouts? This can be a security risk if the PC running RHQ
is left unattended."
--Ian