Fusion continues to ping MG to try to keep the session alive even after the session is gone

[chrisclaydon]

Create an MG Fusion layout, open it in a browser, and either let it sit long enough, or re-start the MG server.

Fusion has a session keep-alive function that pings the MG server periodically. However, it continues to do this indefinitely, even if the session is no longer valid, and fills up the MG server error log with "Session has expired or is invalid" errors.

[zspitzer]

I don't think there isn't an easy way to determine if a mapguide session is valid

 http://trac.osgeo.org/mapguide/ticket/529

[chrisclaydon]

It should be possible to use the new RESOURCEEXISTS request to check the existence of the session-resident map resource.

[madair]

still an issue? I left a web layout open overnight and in the morning the app still worked fine. Restarting the MG service after that did cause the app to hang but that seems like an expected failure mode if the server goes down.

[chrisclaydon]

This is still an issue. If you need to re-start the server for some reason, any open fusion viewers will fill up the error log with session expired messages.

We need to examine the response to the ping request, and if the session is no longer valid, stop pinging until Fusion establishes a new session (presumably through a browser refresh).

[madair]

fixed in [2205]