Hi,
While messing with some code exercised in the webapp, I found that a
whole lot of normal web-app logging was going to webapp/web-map.log,
rather than web.log like it should (at least in my opinion)
Is anyone seeing this in production/real-life, or is it just me? I
think it's due to a whole lot of code in org.opennms.web.map doing:
ThreadCategory.setPrefix(MapsConstants.LOG4J_CATEGORY);
namely, most/all of the Servlet handleRequest methods in
org.opennms.web.map, and also more painful places like the constructors
of org.opennms.web.map.config.MapPropertiesFactory,
org.opennms.web.map.db.DBManager, and
org.opennms.web.map.db.ManagerDefaultImpl,
which get created by Spring at Jetty initialisation time (first servlet
call).
I'm pretty sure it shouldn't be so haphazard about calling
ThreadCategory.setPrefix, because that sets the prefix for that thread
for the rest of it's life (which can and is well beyond the lifetime of
the map handling code).
Any ideas what the best fix is? In all those places, we could store the
prefix before and restore it afterwards, but that seems a little ugly to
me. Do we even need web-map.log as a separate log file?
Ta,
Craig Miskell
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
