Hi List,
I’m wondering if it’s possible to get GeoServer to log less to its log, at least when the user has set it to “production_logging” as I have. The problem is that every time I restart GeoServer (daily) I get a wall of WARN level events.
This is a problem from a sys-admins perspective because it makes it harder to create a simple script which looks for activity in the logs and sends an alert.
The following are the entries that I don’t believe I (as a user/admin) can do anything about:
2013-12-17 06:05:01,509 WARN [support.DisposableBeanAdapter] - Invocation of destroy method failed on bean with name ‘geoServerLoader’: org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name ‘GWCLifeCycleHandler’: Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)
2013-12-17 06:05:02,336 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS[“WGS84 / Simple Mercator”, GEOGCS[“WGS 84”, DATUM[“WGS_1984”, SPHEROID[“WGS_1984”, 6378137.0, 298.257223563]], PRIMEM[“Greenwich”, 0.0], UNIT[“degree”, 0.017453292519943295]], PROJECTION[“Mercator_1SP_Google”], PARAMETER[“latitude_of_origin”, 0.0], PARAMETER[“central_meridian”, 0.0], PARAMETER[“scale_factor”, 1.0], PARAMETER[“false_easting”, 0.0], PARAMETER[“false_northing”, 0.0], UNIT[“m”, 1.0], AXIS[“x”, EAST], AXIS[“y”, NORTH], AUTHORITY[“EPSG”,“54004”]]
2013-12-17 06:05:10,479 WARN [geoserver.logging] - Suppressing StdOut logging. If you want to see GeoServer logs, be sure to look in ‘C:\Tomcat_Compass\bin..\instances\instance1\logs\GeoServer.log’
2013-12-17 06:05:11,883 WARN [config.CustomEditorConfigurer] - Passing PropertyEditor instances into CustomEditorConfigurer is deprecated: use PropertyEditorRegistrars or PropertyEditor class names instead. Offending key [org.geotools.util.Version; offending editor instance: org.geoserver.platform.util.VersionPropertyEditor@anonymised.com
2013-12-17 06:05:13,677 WARN [referencing.factory] - Axis elements found in a wkt definition, the force longitude first axis order hint might not be respected:
PROJCS[“WGS84 / Simple Mercator”, GEOGCS[“WGS 84”, DATUM[“WGS_1984”, SPHEROID[“WGS_1984”, 6378137.0, 298.257223563]], PRIMEM[“Greenwich”, 0.0], UNIT[“degree”, 0.017453292519943295]], PROJECTION[“Mercator_1SP_Google”], PARAMETER[“latitude_of_origin”, 0.0], PARAMETER[“central_meridian”, 0.0], PARAMETER[“scale_factor”, 1.0], PARAMETER[“false_easting”, 0.0], PARAMETER[“false_northing”, 0.0], UNIT[“m”, 1.0], AXIS[“x”, EAST], AXIS[“y”, NORTH], AUTHORITY[“EPSG”,“54004”]]
(I’m not even using that projection!)
Following that, there’s then these lines which aren’t clear as to what they mean:
2013-12-17 06:05:15,128 WARN [org.geoserver] - Ignoring store directory ‘layergroups’
2013-12-17 06:05:15,331 WARN [org.geoserver] - Ignoring store directory ‘styles’
2013-12-17 06:05:15,331 WARN [org.geoserver] - Ignoring store directory ‘Oracle Live - OSMM’
2013-12-17 06:05:15,331 WARN [org.geoserver] - Ignoring store directory ‘layergroups’
2013-12-17 06:05:18,170 WARN [org.geoserver] - Ignoring store directory ‘styles’
I don’t think any of the above sets of logging should be in Production logs at all.
And then there’s a list of every single layer telling me that I don’t have a primary key set in my Oracle (I know):
…
2013-12-17 06:05:30,899 WARN [geotools.jdbc] - Failure occurred while looking up the primary key with finder: org.geotools.jdbc.HeuristicPrimaryKeyFinder@anonymised.com
2013-12-17 06:05:30,899 WARN [geotools.jdbc] - No primary key or unique index found for OS_MM_CARTOGRAPHIC_SYMBOL.
2013-12-17 06:05:31,040 WARN [geotools.jdbc] - Unrecognized geometry type DEFAULT falling back on generic ‘GEOMETRY’
…
Ideally that wouldn’t be in there either, but can understand the case for why it could be.
Rather than just unilaterally opening a JIRA, I thought I’d ask the devs - should any of these really be in production logs? Or is this something that could be cleaned up so GeoServer starts clean?
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.
