Java LiveUpdate Downloads folder grows and uses too much disk space.

Article:TECH95644  |  Created: 2009-01-20  |  Updated: 2014-07-22  |  Article URL http://www.symantec.com/docs/TECH95644
Article Type
Technical Solution


Environment

Issue



After installing Symantec Mail Security for Domino 8.0 or Symantec Scan Engine 5.x disk space used by Java Live Update is not freed after updates are processed by Symantec Mail Security or Symantec Scan Engine.

Symptoms
Java LiveUpdate downloads folder (C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\Downloads\) continues to grow in size. Disk space may run out on the system because of this.


 


Cause



By default Java LiveUpdate downloads and retains 2 gigabytes of cache.


Solution



If the Downloads directory is using more than 2gigabytes of space please see the following document: LiveUpdate Does Not Work With SMSDOM 8.x.Database 'Enterprise Gateways Knowledge Base', View 'Support\All Documents (CLF)', Document 'LiveUpdate Does Not Work With SMSDOM 8.x'

To resolve this issue you can either change the cache size or stop caching all together.


NOTE: If you use Symantec Scan Engine 5.2.10 or greater, Skip to Steps for changing cache size for SSE5.2.10 or greater and Steps for disabling cache for SSE5.2.10 or greater . Java LiveUpdate configuration editor will not update the SSE-specific, separate liveupdate.conf saved under SSE's root directory/folder, so they should be changed manually.

Reference:
KB TECH152863 http://www.symantec.com/docs/TECH152863 


Steps for changing cache size:
1. Run the Java LiveUpdate configuration editor. If using a 32bit Windows operating system type:
     Java -classpath "c:\program files\common files\symantec shared\Java LiveUpdate\jlu.jar" ConfigEditor
     or if using a 64bit Windows operating system type the following command in:
     Java -classpath "c:\program files(x86)\common files\symantec shared\Java LiveUpdate\jlu.jar" ConfigEditor
2. Select Add New Property
3. For Name type: downloadCacheSize
4. For Value type in your desired cache size in bytes. If you type 5368709120, the cache will grow to about 5GB.
5. Select Save


Steps for disabling cache:
1. Run the Java LiveUpdate configuration editor. If using a 32bit Windows operating system type:
     Java -classpath "c:\program files\common files\symantec shared\Java LiveUpdate\jlu.jar" ConfigEditor
     or if using a 64bit Windows operating system type the following command in:
     Java -classpath "c:\program files(x86)\common files\symantec shared\Java LiveUpdate\jlu.jar" ConfigEditor
2. Select Add New Property
3. For Name type: cacheMode
4. For Value type: false
5. Select Save

With the above commands, ensure that the case sensitivity is maintained in the entries or they will not work at all.

Steps for changing cache size for SSE5.2.10 or greater

  1. Locate and open liveupdate.conf with a text editor:

    Windows 32-bit: %ProgramFiles%\Symantec\Scan Engine\liveupdate.conf
    Windows 64-bit: %ProgramFiles(x86)%\Symantec\Scan Engine\liveupdate.conf
    Solaris/Linux: /opt/SYMCScan/bin/liveupdate.conf
     
  2. At the bottom of the file, on a new line, add parameter "downloadCacheSize=" (case-sensitive) and its cache size in byte. In the following example, 5GB (5*1024*1024*1024 = 5368709120 bytes) is allocated.
    NOTE: Do not add any comment tailing the parameter. The parameter will not be properly recognized.

    downloadCacheSize=5368709120
  3. Save liveupdate.conf.

Steps for disabling cache for SSE5.2.10 or greater 

  1. Locate and open liveupdate.conf with a text editor:

    Windows 32-bit: %ProgramFiles%\Symantec\Scan Engine\liveupdate.conf
    Windows 64-bit: %ProgramFiles(x86)%\Symantec\Scan Engine\liveupdate.conf
    Solaris/Linux: /opt/SYMCScan/bin/liveupdate.conf
     
  2. At the bottom of the file, on a new line, add parameter "cacheMode=" (case-sensitive) and its boolean value, true or false, all in lower cases. In the following example, false ("do not cache") is set.
    NOTE: Do not add any comment tailing the parameter. The parameter will not be properly recognized.

    cacheMode=false
  3. Save liveupdate.conf.

With the above commands, ensure that the case sensitivity is maintained in the entries or they will not work at all.


 




Legacy ID



2009082007544354


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


Terms of use for this information are found in Legal Notices