Clients losing connection and object selections after server reload

[#1]

Hi,

We have an issue where clients lose connection and have their selections cleared when a reload is initiated from our QV server. If there are frequent reloads scheduled then this would be a user experience issue. Is there a way to prevent users from having their selections wiped out?

Thanks!

[rwunderlich]

Tyler,

Unchecking the option can increase the RAM usage of the server. WIth the option checked, there can only be one version of a qvw ("Sales.qvw") in server memory. With the option unchecked, you can wind up with multiple versions of Sales.qvw loaded into memory.

UserA - opens Sales.qvw (call this version 1).
Scheduled Reload for Sales.qvw runs creating a "new version 2".
UserB opens Sales.qvw -- will get current version which is now Version 2.

Both version 1 and version 2 are in RAM, occupying twice the RAM of a single copy.

Is it possible that a single user could have both versions open on different screens? It's possible, depending on which client is used and how the open is done. However, the screen containing the first version should get an automatic refresh or refresh notifcation --depending on document option.

-Rob

[#3]

Hi guys,

We've tried out Rob's suggestion for a week now. In my view, the combination of keeping more than one copy in memory and prompting the user to refresh the data when they are logged in - is a passable workaround. At the least, it keeps them from being surprised rather.

Although, we have a working recommendation to always select "No' once the refresh prompt is encountered, since the refresh time takes too long.

We could also afford this since we are using a single document (but really big) to consolidate our data... we may change settings if we decide to have more documents.

It's too bad that there seems to be no way not to refresh the data at all (or is there?).

Also, thanks Rob, for the insight about the effect on RAM usage of multiple versions of the file - this really helps us learn and monitor system performance in relation to usage loads.

[#4]

Hi Rob, I am trying to put in place a process that let the user decide to refresh the data while he is performing selections.

I tried to use the prompt dialog and have the one version unchecked , but it does not seem to work using Aajx .

Is there any other solution ?

Thanks

Philippe

[#5]

What happens to the in server memory if a new document is added to the server? I have noticed that it does update the access page, but was curious about how it effect the RAM.

[p_verkooijen]

If user 1 with the "old" data closes his session the "new" document will not be loaded into RAM untill someone opens it.

If user 1 is still analyzing, and a user 2 opens the document both documents will be loaded into memory.

depending on the number of users and reload schedule, there could be even more than 2 documents in memory.

if the refresh takes to long, maybe you could set the document as preloaded. However I'm not sure this works in combination with allowing multiple versions in memory.