To answer your questions.
1. If you have debug logging enable on QVS you should see the document being unloaded from memory. However, the timeout setting only starts when the last person logs out of the QVW and if someone logs back into the document it will start over when the the last person logs out.
2. 3. 4. The System Monitor application can help you with this information. You can download it here.
Thanks for your response Bill,
I have two SMA's (three now thank you, will look at this today) and am logging all aspects of QVS at high level. Although I'm trying to find that elusive message or field that denotes a QVW dropping from memory.
We are using both Inactive and Total session timeouts. Data is refreshed but we don't want to force people to reload the dashboard every 10 mins, instead we give them the option to refresh. Just before the hour is up a macro opens a text box that can't be moved or minimized (rendering the dashboard unusable) asking them to refresh and after an hour of inactive they "should" be kicked out of the app.....
This is where we have concerns. Because we're refreshing so frequently but don't ask people to take the latest data we expect there's multiple versions of the same dashboard being held in memory. After the hour (or 4 hours total) they are either kicked out or refresh to the latest version which would release the app memory.... Trouble is how to prove this is or isn't happening....
Any further support you can offer will be gratefully received.
Chart shows Max(LoadedDocs) for one day. Crash at 3am is the server restart. we have about 20 live apps
More investigation done and help required please everyone.
Looking at some more fields from Performance Log I can generate a chart which at first glance looks like sessions / documents are being dropped.
Ref Docs (which is noted as the number of documents loaded where there is a session) seems to rise and fall as expected.
Active Docs (where there is activity) follows the trend and as expected just below the total
Doc Loads (new documents loaded) again fits nicely into expected trends
Loaded Docs (Total number of documents loaded at the end of the interval) is off the scale and looks like QV is keeping these in memory....
Is it just that I'm not understanding the logs correctly? Help please. Thanks