Hi all,
this is a warning message for those of you using customized log4j property
files to tweak geoserver logging levels.
As a result of working on http://jira.codehaus.org/browse/GEOS-1255, the
mappings from log4j to java.util.logging have changed (improved).
The change adds finer mapping granularity and thus leads to the following side
effects to your current mappings, which you should adjust if you want:
DEBUG log4j level were mapped to FINER, now DEBUG maps to FINE, so if you
expect to get FINER messages from code using java.util.logging just change
DEBUG by TRACE in your property files.
The property files geoserver provides by default were already updated to
reflect the changes, and also the geotools logging levels were adjusted in
order for the GEOTOOLS_DEVELOPER profile to not blow up that much with
renderer messages.
If you have any question or concern do not hesitate to bug me (guess this is
mostly for Saul?),
cheers,
Gabriel
Gabriel,
I'm extremely happy that you've made this change! It means two things:
1) Someone else understands the logging mappings
2) Someone was able to make a sensible change without being too confused
about how it worked
If anything buggy results from it I'll be sure to let you know.
thanks gabriel,
--saul
Gabriel Roldán-4 wrote:
Hi all,
this is a warning message for those of you using customized log4j property
files to tweak geoserver logging levels.
As a result of working on http://jira.codehaus.org/browse/GEOS-1255, the
mappings from log4j to java.util.logging have changed (improved).
The change adds finer mapping granularity and thus leads to the following
side
effects to your current mappings, which you should adjust if you want:
DEBUG log4j level were mapped to FINER, now DEBUG maps to FINE, so if you
expect to get FINER messages from code using java.util.logging just change
DEBUG by TRACE in your property files.
The property files geoserver provides by default were already updated to
reflect the changes, and also the geotools logging levels were adjusted in
order for the GEOTOOLS_DEVELOPER profile to not blow up that much with
renderer messages.
If you have any question or concern do not hesitate to bug me (guess this
is
mostly for Saul?),
cheers,
Gabriel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://www.nabble.com/Changes-in-geoserver-logging-mappings-tf4646960.html#a13276948
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
On Thursday 18 October 2007 05:19:40 pm sfarber wrote:
Gabriel,
I'm extremely happy that you've made this change! It means two things:
1) Someone else understands the logging mappings
2) Someone was able to make a sensible change without being too confused
about how it worked
hey, it was pretty straight forward as usual with your code.
If anything buggy results from it I'll be sure to let you know.
please do.
Gabriel
thanks gabriel,
--saul
Gabriel Roldán-4 wrote:
> Hi all,
>
> this is a warning message for those of you using customized log4j
> property files to tweak geoserver logging levels.
>
> As a result of working on http://jira.codehaus.org/browse/GEOS-1255, the
> mappings from log4j to java.util.logging have changed (improved).
> The change adds finer mapping granularity and thus leads to the following
> side
> effects to your current mappings, which you should adjust if you want:
>
> DEBUG log4j level were mapped to FINER, now DEBUG maps to FINE, so if you
> expect to get FINER messages from code using java.util.logging just
> change DEBUG by TRACE in your property files.
>
> The property files geoserver provides by default were already updated to
> reflect the changes, and also the geotools logging levels were adjusted
> in order for the GEOTOOLS_DEVELOPER profile to not blow up that much with
> renderer messages.
>
> If you have any question or concern do not hesitate to bug me (guess this
> is
> mostly for Saul?),
>
> cheers,
>
> Gabriel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel