> Why are you even caring about it, you should not run GeoServer at that
> logging level to start with (I mean, DEBUG
> is really for developers, if you are running a server like that, you're
> doing it wrong).
>
>
Two reasons:
1) Because I don't think I've seen it before.
2) More importantly, because there are so many that it floods out any
actually useful log entries and in fact because the logs cycle, they get
deleted. I wasn't exaggerating when I said that it writes 10's of MB for
each request. So I'm pre-empting if/when there is something that stops
working and requires me to use Debug level logging - because if that
happens the logs will be useless being filled only with this event.
(This is on my test server - I leave it on debug by default because when
I'm using it I'm often trying to find stuff that's gone wrong).
Hope that clears up my interest.
Cheers,
Jonathan
>
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
