Symantec Workspace Streaming - File Drop to fix DB issue with excess as_rep_session_info records for offline sessions

Article:TECH198516  |  Created: 2012-10-17  |  Updated: 2013-01-23  |  Article URL http://www.symantec.com/docs/TECH198516
Article Type
Technical Solution


Issue



A bug in the Streaming Server ( STS ) code was uncovered related to how the code was acquiring locks while in the process of uploading offline session data into the process queue. This locking process locks all users from being able to start the streaming of an application while potentially another users process is uploading offline session data. If the number of offline records takes more than 30 seconds to upload and process the client times out and resends the offline data report. As the previous report timed out the second try also times out and the client repeats the process. The process loads the server with reports and the DB as_rep_session_info fills up with session data.

 

Error



Users are unable to authenticate


Environment



Server must be running Streaming Server 6.1 SP8 MP1 to apply the file drop


Cause



Offline reports aren't efficiently processes by the server. Rather than having the client wait for the backend to process the data upload, the backend created a thread process to process the report data behind the scenes and returns in a few milliseconds so the client does not timeout and resend the report over and over again, the client wait for the backend to process the data upload the backend created a thread process to process the report data behind the scenes and returns in a few milliseconds so the client does not timeout and resend the report over and over again.


Solution



A work around to fix the problem without applying this fix is to remove all the offline report data from each client machine that is spamming the DB. The data is stored in the HKEY_LOCAL_MACHINE\SOFTWARE\AppStream\AppMgr\Servers\1\OfflineSessionReports regkey. This removal could be accomplished by created a logon script attached to a GPO that will clear the data upon each login.

A server fix was created to resolve this issue. To get the fix contact support.

How to install this point fix (once getting the fix from support)-

Summary:
1. Backup the original files.
2. Replace AWE_Legacy.jar on all servers.
3. Replace AppStreamService.exe on front end servers.
4. Modify ste.conf file on back end server.
 
1. Backup the original files:
Do not rename the original JAR files and leave them in place; this will cause problems as Java scans the directory and loads them regardless of file name and/or extension. You are strongly advised to move the original files to a separate directory.
 
2. AWE_Legacy.jar locations: (all servers)
..\Symantec\Workspace Streaming\Server\agent\lib\AWE_Legacy.jar
..\Symantec\Workspace Streaming\Server\common\apache-tomcat\shared\lib\AWE_Legacy.jar
..\Symantec\WorkspaceStreaming\Server\common\jboss-4.2.2\server\appstream\deploy\ste\ste.jar\AWE_Legacy.jar**
**Note: this directory only exists on the back end server.
 
3. AppStreamService.exe location:(front end servers)
..\Symantec\Workspace Streaming\Server\server\bin\AppStreamService.exe
 
4, Modify ste.conf file: (back end server)
..\Symantec\Workspace Streaming\Server\streamletEngine\conf\ste.conf
 
Add the following entries to the end of the file:
# Persist to disk the offline report and event data
# so it will not be lost if an outage occurs during processing.
offlineReport.persist.data=true
eventReport.persist.data=true
 

Please contact support for the file drop location

Supplemental Materials

SourceETrack
Value2923523, 2861850


Article URL http://www.symantec.com/docs/TECH198516


Terms of use for this information are found in Legal Notices