Video Screencast Help

SEP SBE uses old Java version?

Created: 23 Dec 2011 • Updated: 26 Apr 2012 | 2 comments
This issue has been solved. See solution.

I was checking my server's event logs this morning and came across an application hang (event ID 1002), which states:

The program javaw.exe version 6.0.260.3 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 18b0
 Start Time: 01ccc0cf75cfeea0
 Termination Time: 12
 Application Path: C:\Program Files (x86)\Symantec\Symantec Protection Center\jre\bin\javaw.exe
 Report Id: 35d7d9e2-2cdf-11e1-8c55-bcaec554f425
 

That, to me, looks like Symantec Protection Center uses its own version of Java, which is at version 6.0.26.  There have been a few security updates from Oracle since 6.0.26, and the current version is 6.0.30.  Should Symantec be updating its Java with Oracle's releases?

Comments 2 CommentsJump to latest comment

KV1984's picture

It can also be due to Java heap size being low try increasing the Jave heap size , 

 

HKLM\System\CurrentControlSet\Services\semsrv\Parameters\

 

increase the JVM Option Number 0 and 1 value and see if it works or else you can download the latest java version and install it 

SOLUTION
newkansan's picture

This event has only happened once, so I am not so concerned about fixing the event log error, but the error brings to light that SEP is using a sandboxed version of Java that is a few versions old.  I already have the latest Java installed on this machine, but it appears that Symantec is not using the system version of Java, it's using its sandboxed version.