The STE engine stops prematurely on the backend server
The STE engine stops prematurely on the backend server with the following event:
The SWS Streamlet Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. The java logs will show that the Java tomcat server is running out of memory.
The java tomcat server is running out of memory due to the frontend servers upgrading clients or the frontend server is dealing with to many clients requesting packages.
You can verify that the java server is running out of memory by checking the logs in
C:\Symantec\Workspace Streaming\Server\common\jboss\bin\hs_err_pidxxxx.mdmp C:\Symantec\Workspace Streaming\Server\common\jboss\bin\hs_err_pidxxxx.log
Symantec is aware of this issue and will update this document when a solution becomes available. It is not necessary to log a support case on this issue. Please subscribe to this article to be notified of any updates. WORKAROUND: Increase the Java heap size on each of the frontend servers that run java tomcat. Edit the following regkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASWEStreamletEngine\Param eters 1. Increase the value of JVM Option Count (REG_DWORD) + 1 a. Original value: 12 b. Modified value: 13 2. Create a new string value a.Name: JVM Option Number x (where x is the next cardinal number) b.Data: "-Xss128k" (without the quotes) 3. Restart the STE component for these settings to take effect.