Providing geoscience data globally Navigation
Main content
Bottom links


Home > How to serve a OneGeology WMS > Using GeoServer software to serve OneGeology Web Services > GeoServer troubleshooting

6.7 GeoServer troubleshooting

Q: I made a change in the database on my server and now the service is not working
A: Try clearing the cache and reloading GeoServer on the Server Status page. If that doesn’t work, try hard restarting the service through Apache Tomcat.
Q: Can I use a replicated Feature Class to create a service on GeoServer?
A: No.
Q: I set up my services under three separate workspaces. When I connected to the WMS in ArcCatalog, all the layers appeared as one bundle. Is there a way to separate them out so I can add them individually?
A: Yes.

Though setting up your services under different workspaces seems to imply that they can be accessed as discrete services, GeoServer defaults to providing one capabilities document containing the information for all of the services set up on your instance of GeoServer. To access workspaces individually, you will need customize your Get request to specify the desired workspace.

For example: a Geological Survey might run three services on GeoServer:

  • GeologicUnitView
  • FaultView
  • ContactView

To perform a GetCapabilities request for GeologicUnitView, your GetCapabilities request will appear as follows:

This URL opens the WMS capabilities document for the GeologicUnitView workspace only. A generic form of the service endpoint for the request is as follows:

http://[host server]/geoserver/[Workspace Name]/ows?

Q: Is it possible to configure GeoServer so that I do not need to use PostGIS?
A: Try installing the ArcSDE plug-in for GeoServer. To do this, you will need to download the extension from GeoServer’s website. Make sure to match the versions of the extension and GeoServer. If you can get it to work, you should be able to connect to other SDE databases running on, for instance, MS SQL or Oracle.
Q: All of my data are in Shapefiles. Can I deploy a shapefile as a GeoSciML-Portrayal service?
A: The problem you will run into is the truncation of field names that occurs in shapefiles. Ideally you will have a full version of the data in PostGIS. As mentioned in the above document, to be compliant with GeoSciML-Portrayal, you will need to make sure there is no truncation in field names; they must be an exact match for the GeoSciML-Portrayal schema. To map table fields to XML elements with different names you will have to use the Application Schema extension for GeoServer (

Section last modified: 9 November 2015