Setup is: RHEL 6, GeoServer (war) 2.10.0, Jetty 9.3, PostgreSQL 9.4,
monitoring plugin with hibernate enabled, configured for JNDI datasource
provided by Jetty c3p0
System is under pretty heavy use (1000's of requests per hour) and while
the extension does what its intended to do, we end up with an unstable
GeoServer after several hours and must be restarted. System reports
resident memory slowly increasing unbounded for the java process. At about
2x the max heap size setting it starts to fall over. Services become
unreachable and log starts printing huge lists of threads. Even the
shutdown signal to Jetty seems to be ignored and the process must be
SIGKILL'd.
monitor.properties:
storage=hibernate
mode=history
sync=async
maxBodySize=0
db.properties:
defaultAutoCommit=false
hibernate.properties:
databasePlatform=org.hibernate.dialect.PostgreSQLDialect
database=POSTGRESQL
hibernate.use_sql_comments=true
generateDdl=true
hibernate.format_sql=true
showSql=false
hibernate.generate_statistics=true
hibernate.session_factory_name=SessionFactory
hibernate.hbm2ddl.auto=update
hibernate.bytecode.use_reflection_optimizer=true
hibernate.show_sql=false
I'm curious if this has been reported before if anyone can provide leads as
to the cause. I checked JIRA and didn't see anything. I'm willing to peak
around in the monitor code.
Also, a lot of our users and using KML superoverlays and this causes about
90% of our requests to be operation='dispatch' which seem completely
useless to me. Anyone know what the purpose of that is? I'm interested in
making a configuration parameter to ignore these.
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
[email protected]
------------------------------------------------------------------------------
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
