This is not entirely connected to the issue I created this post for but...
setting "-DGWC_DISKQUOTA_DISABLED=true" in Tomcat configurations helped to
improve performance. From
http://geowebcache.org/docs/1.11.0/configuration/diskquotas.html:
/Note The enabled configuration property only accounts
Although this might not have been the root cause of our issues but I think it
migth be of interest for someone:
/*Note *The enabled configuration property only accounts to whether the
layers should be automatically truncated when the disk quota is exceeded,
and to do so the disk usage statistics
Hi,
thanks for following up. Hum.. in this case I don't know what it could be,
if you can,
try to reproduce the issue on a standard geoserver installation (the
default data dir)
with step by step instructions on how to reproduce, and then open a bug
report
with the details.
I know it can be quite
Hi, thanks for the warning. I don't know what is "email setup" and what do
you mean by "client"?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5317143.html
Sent from the GeoServer - User mailing list archive at
Changing "Disk quota check frequency" from 10s to 100s did fix the problem.
It looks as if triggered series of crashes because one of Tomcat's crashed
several times during one day period.
--
View this message in context:
Changing "Disk quota check frequency" from 10s to 100s did NOT fix the
problem. It looks as if triggered series of crashes because one of Tomcat's
crashed several times during one day period.
--
View this message in context:
Dear Julius,
just wanted to warn you that your emails are marked as spam at least by
google accounts.
Could it be a problem caused by how you setup your email address or client?
Best Regards,
Alessio Fabiani.
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for
Linux 5
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5316982.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
--
Tomcat log after latest crash https://ufile.io/db33d1
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5317003.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Oracle Linux Server release 6.8
NAME="Oracle Linux Server"
VERSION="6.8"
ID="ol"
VERSION_ID="6.8"
PRETTY_NAME="Oracle Linux Server 6.8"
Will try
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5316238.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
--
What Linux distribution do you use?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5316242.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Did you try increasing the disk quota interval check, regardless of whether
it's enabled or not?
There might be a bug that starts those threads even if the quota is
disabled, for example.
Cheers
Andrea
On Mon, Apr 3, 2017 at 1:23 PM, user154654 wrote:
> No solution found...
No solution found...
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5315430.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
For dracic:
I was told that Tomcat is managed with root user. So what "ulimi" command
printed should be exactly what you asked for (right?).
You said "Limit of 1024 max open files is too low for GWC in heavy use". I
am not sure that is the case because our test applications should be under
less
Limit of 1024 max open files is too low for GWC in heavy use. You should set
it to unlimited.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5311451.html
Sent from the GeoServer - User mailing list archive at
I see now that you posted limits for root account. You should check for
tomcat user, or account that is used for tomcat service. I don't see which
distro you use...
--
View this message in context:
[root@gislin3par ~]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 120365
max locked memory (kbytes, -l) 64
max memory
As I understand since disc quota is not enabled this is not it. Despite the
printscreen info I asked admin to run the command
and I should get answer shortly.
Maybe I shoud have specified what "couple more applications" meant when
describing the isssue first. On one machine there are 3 Tomcats
Sorry for not responding sooner, I was on another project (since these
crashes happen on test applications which are not priority) and forgot about
this issue. Printscreen of disc quota params http://prntscr.com/eh2n28 .
Same parameters are used in PROD application which does not crash.
--
View
Please send us output of the command:
su - tomcat -c "ulimit -a"
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-9-2-GC-overhead-limit-exceeded-tp5306122p5310552.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi,
did you try it, did it help? I would like to open a ticket about this (to
avoid the disk quota cleaner thread accumulation)
but first need confirmation that this is indeed the problem
Cheers
Andrea
On Wed, Mar 1, 2017 at 6:16 PM, Andrea Aime
wrote:
> Hi,
> I
Hi,
I just had a very quick look, the dump contents are quite weird, it seems
there is a
giant list of tasks to clean the GWC tiles to respect the quota using all
the memory.
Is it possible that you configured a very short time in the disk quota check
frequency, something like 1 second? So short
Got the dump. It is at https://sndt.gl/42Nzl1OR2EkyU. They keep files for 7
days, so if it will no longer be available by the time someone has time to
take a look at the dump, just let me know.
--
View this message in context:
Thank you for your suggestions, I have finally received .jar list:
/imageio-ext-arcgrid-1.1.15.jar
imageio-ext-gdalarcbinarygrid-1.1.15.jar
imageio-ext-gdal-bindings-1.9.2.jar
imageio-ext-gdaldted-1.1.15.jar
imageio-ext-gdalecw-1.1.15.jar
imageio-ext-gdalecwjp2-1.1.15.jar
Hi,
I've seen this kind of error in the past, it's a weird case of OOM,
normally caused by
object waiting in the finalization queue to be released, and taking their
time to run
the "finalize" method.
It's hard to say what might be the cause, for me last time it was a lot of
concurrent requests
Hello. I have Tomcat 8.5.6 + Java 8 running with a geoserver and a couple
more applications. Problem is that server keeps crashing. When inspecting
catalina.out logs I see:
*1)* Exception in thread "ajp-nio-8011-ClientPoller-1"
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
27 matches
Mail list logo