I am sure this list can be toned down, and I like the goal of making "GeoServer
start clean".
Lets have a look...
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!)
This looks to be a mistake that can be cleaned up.
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"]]
There are two reasons why WKT would be used:
a) one of your layers uses an "prj" file - in which case this warning is fair
b) geoserver, or your installation, includes additional custom definitions in
an epsg.properties files - in which case this warning is far. However for the
"built-in" additional codes we can probably suppress these warnings while
parsing the file.
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'
I expect this could be set to INFO.
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@3f9872ad
Looks to be something to fix.
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!)
Same deal as above, you can remove it from your data directory epsg.properties
file if you are not using it.
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'
Not sure either, something to fix in code or configuration?
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.
I think we should clean up our example configuration so they do not occur, so
if these warnings are useful in a production setting they will be respected.
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@3a4b8c89
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.
Think we could make an extra connection parameter here, the default setting can
produce the warnings, and provide an explicit setting to handle the "I know"
case.
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?
I have a similar JIRA issue open about the initial release configuration, more
about useful example/defaults.
This would be a good thing to target for 2.5 ... if you think we can crush
these warnings by next release. You may want to put this forward as a GSIP
since it would require collaboration across a number of modules.
Jody
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
