Java(TM) Platform SE binary system process

Permanently deleted user

09 Juni 2017 02:15

I have a Java(TM) Platform SE binary system process running continuously on my Geocortex server taking up 45-50% CPU. The process is linked to the java.exe found at "C:\Program Files\Latitude Geographics\Geocortex Core\NSRoot\Geocortex\Core\Roles\DocumentStore\3.0.1.1294\Java\jre1.8.0_45\bin\". It is causing workflows within my viewers to run really slowly and it is generating huge log files (GB in size) in "C:\Program Files\Latitude Geographics\Geocortex Application Services 2\Data\Logs".

 

I have Instant Search turned off on all layers in all my sites, so there should be any indexing going on. I'm not sure ow it started, but rebooting the server does not fix the issue.

 

The server has 3 instances of GE4.4 and one instance of GE4.6. It is running Windows Server 2012 R2 Standard.

 

Has anyone else had this problem? 

 

Thanks,

 

Dave

0

• 

  Permanently deleted user

  09 Juni 2017 15:09

  Hi Dave,

   

  It's not too unusual for that Java process to use a lot of system resources (as it is running Elasticsearch, which is pretty CPU and RAM intensive), however if you are seeing log files that are growing rapidly, it sounds like it may be a bug to me.  Could you please open a support case so we can help you investigate?

   

  It may also be that the server is under powered (Although that would account for the CPU usage, and not the large log files).  How much RAM and how many CPU cores are assigned to the machine?

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  12 Juni 2017 07:55

  Hi Danny,

   

  I raised the issue with our local vendor and they said that there is a known issue with GE v4.6.0/v4.6.1 that matched the issue I'm having:

   

  CORE-2373: High CPU and memory usage when reconnecting to document store

   

  Most of the log files that had been generated were too big to open in a text editor, but I did manage to open one and it referred to connection failures with the document store and something to do with the elastic search.

   

  They said the problem is fixed in v4.6.3 so I'm going to upgrade to that version and see what happens.

   

  Thanks,

   

  Dave

  0

Du måste logga in om du vill lämna en kommentar.