ClassCast Exception after restarting geoserver using the community schema

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Application schema
  • Labels:
    None

Description

We were doing some experiments today with a Geoserver running the community module. At the beginning we had one complex datastore configured and serving one featuretype.

When I configure a complex data store (siteLocation) usually everything works fine, until Geoserver is restarted. After the restart the datastore doesn't work anymore and deleting it and reconfiguring doesn't help. Neither does restarting Geoserver again.

To get a working Geoserver again the only option I found so far, is replacing the data directory with a fresh copy. Maybe it gets somehow corrupt??

Here is a snippet from geoserver.log. It shows the logs when it tries to restart geoserver.

ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it
2008-05-02 15:51:55,267 INFO [geoserver.global] - StdOut logging enabled. Log file also output to 'C:\stuff\DuckHawk\AWDIP\datadir\geoserver_conf\logs\geoserver.log'
2008-05-02 15:51:55,847 INFO [geoserver.global] - Loading feature type 'bom:::SiteLocation' (layer 1/1)
2008-05-02 15:52:00,407 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/om/1.0', as it couldn't be resolved for the provided location path 'http://schemas.opengis.net/om/1.0.0/om.xsd'
2008-05-02 15:52:00,940 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/om/1.0', as it couldn't be resolved for the provided location path './observation.xsd'
2008-05-02 15:52:00,956 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/sampling/1.0', as it couldn't be resolved for the provided location path 'http://schemas.opengis.net/sampling/1.0.0/sampling.xsd'
2008-05-02 15:52:01,206 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/sampling/1.0', as it couldn't be resolved for the provided location path './samplingManifold.xsd'
2008-05-02 15:52:01,206 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/sampling/1.0', as it couldn't be resolved for the provided location path './specimen.xsd'
2008-05-02 15:52:01,206 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/cv/0.2.1', as it couldn't be resolved for the provided location path 'http://bp.schemas.opengis.net/06-188r1/cv/0.2.1/cv.xsd'
2008-05-02 15:52:01,708 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/cv/0.2.1', as it couldn't be resolved for the provided location path './compactDiscreteCoverage.xsd'
2008-05-02 15:52:01,708 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path 'http://schemas.opengis.net/sweCommon/1.0.1/swe.xsd'
2008-05-02 15:52:01,943 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './positionTypes.xsd'
2008-05-02 15:52:01,943 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './curveTypes.xsd'
2008-05-02 15:52:01,958 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './data.xsd'
2008-05-02 15:52:01,958 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './temporalAggregates.xsd'
2008-05-02 15:52:01,958 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './phenomenon.xsd'
2008-05-02 15:52:01,958 WARN [geotools.xml] - Using the provided absolute URI as the location for namespace 'http://www.opengis.net/swe/1.0.1', as it couldn't be resolved for the provided location path './xmlData.xsd'
2008-05-02 15:52:03,698 WARN [complex.config] - http://www.opengis.net/sampling/1.0SamplingPointType has no super type
2008-05-02 15:52:03,698 WARN [complex.config] - http://www.opengis.net/om/1.0ObservationType has no super type
2008-05-02 15:52:03,698 WARN [complex.config] - http://www.opengis.net/cv/0.2.1CompactDiscreteTimeCoveragePropertyType has no super type
2008-05-02 15:52:05,124 ERROR [geoserver.global] - FeatureTypeInfo bom:::SiteLocation ignored - as DataStore bom is broken:java.lang.ClassCastException: org.geotools.feature.iso.type.ComplexTypeImpl cannot be cast to org.opengis.feature.type.FeatureType
2008-05-02 15:52:06,236 ERROR [data.jdbc] - There's code using JDBC based datastore and not disposing them. This may lead to temporary loss of database connections. Please make sure all data access code calls DataStore.dispose() before freeing all references to it

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. GEOT-1796 ComplexDataStore not disposing JDBC connections

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. GEOS-1904 Dump data loading stack traces with a normal logging configuration, as it is now it makes error diagnosis just too hard

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ben Caradoc-Davies added a comment -

The JDBC errors are those reported in GEOT-1796. These are likely unrelated to the GeoServer data directory corruption[?] issue.

Show
Ben Caradoc-Davies added a comment - The JDBC errors are those reported in GEOT-1796. These are likely unrelated to the GeoServer data directory corruption[?] issue.
Hide
Permalink
Andrea Aime added a comment -

Looking into the code that's eating the exception I noticed that a full stack trace will be dumped into the logs only if you setup logging to its fullest. Try to set it to the "geoserver_developer" configuration and restart, this time, buried into a ton of logging, you should get the full stack trace

Show
Andrea Aime added a comment - Looking into the code that's eating the exception I noticed that a full stack trace will be dumped into the logs only if you setup logging to its fullest. Try to set it to the "geoserver_developer" configuration and restart, this time, buried into a ton of logging, you should get the full stack trace
Hide
Permalink
Stefan Hansen added a comment -

It is not possible to set any configuration of the server itself in the community schema version I use. Does anyone know why?

Show
Stefan Hansen added a comment - It is not possible to set any configuration of the server itself in the community schema version I use. Does anyone know why?
Hide
Permalink
Ben Caradoc-Davies added a comment -

It is broken in my community-schema version as well. There are no options under the admin page. Because the UI cannot be used to configure community-schema mappings, it is neglected.

Show
Ben Caradoc-Davies added a comment - It is broken in my community-schema version as well. There are no options under the admin page. Because the UI cannot be used to configure community-schema mappings, it is neglected.
Hide
Permalink
Ben Caradoc-Davies added a comment -

Stefan, I understand that you have resolved your issue with GeoServer not restarting? (Broken relative paths?) If so, please let me know and I will close this issue.

Show
Ben Caradoc-Davies added a comment - Stefan, I understand that you have resolved your issue with GeoServer not restarting? (Broken relative paths?) If so, please let me know and I will close this issue.
Hide
Permalink
Stefan Hansen added a comment -

I wouldn't say the issue has been solved, but it can be easily avoided. I would suggest we change the priority to something very low, but keep the issue open. That a config-file outside the featuretypes folder can be used to configure a datastore that is working, but only until Geoserver gets restarted, is in my opinion something that should be fixed in the future, but probably not immediately.

Do you want me to open an issue for the broken UI-interface or is there already one?

Show
Stefan Hansen added a comment - I wouldn't say the issue has been solved, but it can be easily avoided. I would suggest we change the priority to something very low, but keep the issue open. That a config-file outside the featuretypes folder can be used to configure a datastore that is working, but only until Geoserver gets restarted, is in my opinion something that should be fixed in the future, but probably not immediately. Do you want me to open an issue for the broken UI-interface or is there already one?
Hide
Permalink
Ben Caradoc-Davies added a comment -

Stefan, please open a new geoserver issue for the broken UI, if there is not already one.

Show
Ben Caradoc-Davies added a comment - Stefan, please open a new geoserver issue for the broken UI, if there is not already one.
Hide
Permalink
Ben Caradoc-Davies added a comment -

I think this issue is stale. Can anyone reproduce on trunk or 2.0-RC1?

Show
Ben Caradoc-Davies added a comment - I think this issue is stale. Can anyone reproduce on trunk or 2.0-RC1?
Hide
Permalink
Andrea Aime added a comment -

Closing as there has been no feedback from the reporter for significant time

Show
Andrea Aime added a comment - Closing as there has been no feedback from the reporter for significant time

People

  • Assignee:
    Ben Caradoc-Davies
    Reporter:
    Stefan Hansen
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: