Andrea:
I did run into these kind of issues where loggers created too soon were
set up with a java util logger before we could get in there and supply a
logging factory. I found the 'easiest' way to trace the problem was to put
in a breakpoint where the logger was created (and trace back to see the
responsible code).
I tried using a JAI_LOGGING.xml based on GEOTOOLS_LOGGING.xml and adding
the following. I did not see any java.media.jai messages.
<Logger name="javax.media.jai" level="debug" additivity="false">
<AppenderRef ref="stdout"/>
<AppenderRef ref="geoserverlogfile"/>
</Logger>
I am not sure if their is a regression here or not, Do you have a reliable
way to make a JAI exception?
--
Jody Garnett
On May 17, 2022 at 10:46:02 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi Jody,
> I was debugging some JAI code and think I've found a regression (but I'm
> not 100% sure).
> I'm dealing with a case where an exception is thrown in JAI code, and even
> setting the logging level to "VERBOSE",
> the JAI errors are not getting logged... and I believe they were, before
> (this is the part I'm not 100% sure about).
>
> The imaging listener does not seem to have been touched during the Log4J2
> refactor:
>
> https://github.com/geoserver/geoserver/blob/7c52ac99e607e84294c8de40f1ad403753e930e6/src/main/src/main/java/org/geoserver/GeoserverInitStartupListener.java#L95
>
> Thinking out loud:
>
> - Timing issue? The logger is likely grabbed before the logging can be
> initialized
> - Configuration issue? Maybe the log profiles used to load the
> "javax.media.jai" package and now they don't anymore
>
> Jody, does this ring a bell to you?
>
> Cheers
> Andrea
>
>
> On Tue, May 10, 2022 at 6:15 AM Jody Garnett <jody.garn...@gmail.com>
> wrote:
>
>> The GeoServer 2.21 <http://geoserver.org/release/2.20-RC/>
>> http://geoserver.org/release/2.21-RC/-RC Release Candidate is
>> available for testing, see release announcement
>> <https://geoserver.org/announcements/2022/05/09/geoserver-2-21-RC-released.html>
>> for
>> a tour of what is new, improved and fixed!
>>
>>
>> - Feature Type Customization - one of my favourite features has
>> returned from GeoServer 1 much improved with ability to dynamically
>> generate attributes!
>> - A language chooser has been added! / Un sélecteur de langue a été
>> ajouté !
>> - You can now define styles for SINGLE or OPAQUE layer groups (each
>> style can gather together the content and styling needed to produce the
>> correct visual)
>> - GeoPackage WMS and WFS Output (for WPS output we recommend the WPS
>> Downloader extension)
>> - Log4J update, along with Logging REST API and user interface
>> control of request logging.
>> The log4j upgrade supported by activity sponsors opengeogroep.nl,
>> www.terrestris.de, how2map.com, www.geonovation.nl
>> - WPS KML input/output
>> - GDAL 3.x compatibility for those using gdal bridge
>>
>>
>> Thanks to Jody Garnett (GeoCat) for working on this release, and to
>> everyone who has contributed to what is a fantastic update :)
>>
>> Helping test a release candidate is your chance to contribute directly
>> providing testing and feedback on new functionality (and double checking if
>> your favourite bug is fixed.)
>>
>> We ask everyone (individuals, organizations, service providers) to:
>>
>> 1. Download the release candidate
>> <https://geoserver.org/release/2.21-RC/>
>> 2. Test with your own data
>> 3. Reply to this email (even just to say hi)
>>
>> Participating in testing release candidates is a key expectation of our open
>> source social contract <http://www.ianturton.com/talks/foss4g.html#/>.
>>
>> - Helping test is the minimal price of admonition for GeoServer,
>> don't be cheap share your time!
>> - It also just makes good risk management sense; help making a
>> stronger GeoServer
>> - We make an effort to thank each person who tests in our release
>> announcement
>> and project presentations.
>> - GeoServer commercial service providers
>> <http://geoserver.org/support/> are fully expected to test on behalf
>> of their customers.
>>
>>
>> --
>> GeoServer Project Steering Committee
>> _______________________________________________
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob: +39 333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
