Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

The memory held by QVS keeps rising because QVS keeps loading already loaded docs into memory for two users.

Specs:

  • Qv Server 8.5
  • Server: 64bit, 256GB RAM, 4 8-Core hyperthread CPUs
  • Windows Server 2008 R2
  • IE Plugin Client 8.5 (latest release)

Here's the log seeing the following in the QVS EVENT.log:

EventID Message Severity Timestamp
302CAL usage: Named CAL "LEINTERNAL\TLWATER" unused - remaining count = 0.Warning2010-10-22 12:59:29
302CAL usage: Named CAL "LEINTERNAL\TLWATER" unused - remaining count = 1.Warning2010-10-22 12:59:12
302CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 0.Warning2010-10-22 12:54:57
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:47:40
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:46:06
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:44:30
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:43:28
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:42:08
108The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.Information2010-10-22 12:40:50
302CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 0.Warning2010-10-22 12:38:50
302CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 1.Warning2010-10-22 12:38:50
108The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.Information2010-10-22 12:35:45
108The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.Information2010-10-22 12:34:21
108The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.Information2010-10-22 12:32:53
108The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.Information2010-10-22 12:28:59


We can't put users on this new server until we can resolve this. Any ideas?!

Thanks, Tyler

13 Replies
Not applicable
Author

Hi Tyler,

Document Timeout (minutes): "30" preserves the document in the memory for 30 minutes from the time the user is not (!) using it anymore. So if this user reopens it within the next 30 mins (lets say 28 minutes) it opens quicker, as it does not require to be reloaded into memory. Thus it was "wasting" RAM Memory for 28 minutes for the benefit oft reopening faster, if the user needs it again. If it is not reopened, it was wasting the ram for 30 minutes for nothing.

At least that is the way I understand this option.

I have set the Document Timeout (minutes) value to 2 minutes.

The other timeout options should rather not be set to such short periods like 2 minutes as this will kick users, when they do their coffe break!

Not applicable
Author

So if document timeout is 30 mins - in my case - why are my loadedDocs rising every time a reload is done? Is this timeout for "LoadedDocs" ? I am getting 12 LoadedDocs added every hour (60/5= 12 on a 5 minute reload) I have gone from 111 to 123 in past hour for instance - why wont they time out?

Anonymous
Not applicable
Author

Have you restarted the QV Services after making the "Document Timeout" changes? If not, I believe you will need to restart to make the new value live.

Also, the document must be idle for 30 minutes. If they are in use they will not go away.

Not applicable
Author

Thanks - I have just restarted it - so I will see how it progresses for the day.