|
Bruce Simons created an issue |
Issue Type: |
|
---|---|
Affects Versions: |
1.2.5 |
Assignee: |
Unassigned |
Attachments: |
geoserver.log-1.txt |
Components: |
Application schema |
Created: |
15/May/15 7:19 AM |
Environment: |
PostgreSQL 9.3 |
Priority: |
|
Reporter: |
When using Geoserver app-schema I am getting the following errors:
{requested feature type}&outputFormat=gml32&featureID={feature ID}
&outputFormat=gml32&maxFeatures=1 Stopping and starting TomCat (without changing any Geoserver configuration files) will eventually result in a correctly populated response, although requests to other features that previously worked, may now fail and return the above errors. Once the feature request is not giving the FID error it seems to continue working until restarted. When the configuration is one Feature with no feature links it doesn’t seem to fail (although the maxFeatures=5 is slow), but adding a single FEATURE_LINK can give (but not always) the FID error. I’m not accessing app-schema feature types using “workspace-specific” service URLs. Not sure if this is related, but layer preview for the service also fails (example from externally facing service): |
This message was sent by Atlassian JIRA (v6.5-OD-03-002#65000-sha1:b8f65f8) |
|