Dear colleagues

I'm a Junior Geoserver/Jetty 2.11.0 admin and I'm facing this crash on 
my Geoserver/Jetty setup running on a 32GB RAM CentOS7 VM provided by 
Hetzner [§] :


$ egrep webcache  lsof.txt  | grep CLOSE_WAIT | tail
...
java       8403 15947   geoserver 1015u     IPv6             332956 
  0t0                  TCP 
localhost.localdomain:webcache->localhost.localdomain:34244 (CLOSE_WAIT)
java       8403 15947   geoserver 1016u     IPv6             332959 
  0t0                  TCP 
localhost.localdomain:webcache->localhost.localdomain:34246 (CLOSE_WAIT)
java       8403 15947   geoserver 1017u     IPv6             332996 
  0t0                  TCP 
localhost.localdomain:webcache->localhost.localdomain:34248 (CLOSE_WAIT)


$ egrep webcache  lsof.txt  | grep CLOSE_WAIT -c
169257


PID 8403 is Geoserver :

geoserv+  8403  6.4 56.7 23500896 18603080 ?   Ssl  Apr11  82:52 java 
-DGEOSERVER_DATA_DIR=/usr/share/geoserver/data_dir 
-Djava.awt.headless=true -DSTOP.PORT=8079 -DSTOP.KEY=geoserver 
-Djavax.net.ssl.trustStore=/etc/pki/java/cacerts -Xms8G -Xmx16G 
-XX:SoftRefLRUPolicyMSPerMB=36000 -XX:+UseG1GC -jar start.jar


$ java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)


to fix it I'm forced to restart Geoserver, until its next crash.


kindly what may I check ?


I can certainly provide more logs/stats/files if it's needed.

I might also distribute the Geoserver components into other 32GB RAM 
CentOS7 VMs in order to avoid the recurring crashes.


many thanks in advance for any advise,
kind regards
Fabio Martinelli

[§] https://hetzner.de/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to