Affects Version/s: 2.13.0
Fix Version/s: None
Using the /classify endpoint against our layers, we discovered some worked fine, and others returned 500.
After some testing, we determined that the cause of this has to do with whether the corresponding classify operation (WPS) returns an empty list (or null). So, this can happen for a feature type with no records (empty table), or if the attribute specified is invalid, or only contains null values.
The "fix" in this case is probably just better error handling, and a helpful message returned to the client.
If I do:
HTTP ERROR 500
Problem accessing /geoserver/rest/sldservice/cidne/classify.xml. Reason: