Actions
Incident #11871
closed
PAIM- geoserver: the id of geoserver running instance is the same for all the geoserver instances of PAIM VRE
Status:
Closed
Priority:
Normal
Assignee:
Category:
System Application
Target version:
Start date:
Jun 04, 2018
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Production
Description
All the Geoserver instances of PAIM, have the same resource id:
geoserver-protectedareaimpactmaps.d4science.org geoserver1-protectedareaimpactmaps.d4science.org geoserver2-protectedareaimpactmaps.d4science.org
This means that there are only one resource registered to the IS and not three as expected.
In addition the resource is replaced when an instance try to publish/update its profile.
The id of the RunningInstance is the following:
e12651da-e958-4bc9-9cf2-147259e78051
Updated by Roberto Cirillo almost 7 years ago
- Subject changed from PAIM- geoserver: the geoserver running instance is the same for all the geoserver instances of PAIM VRE to PAIM- geoserver: the id of geoserver running instance is the same for all the geoserver instances of PAIM VRE
Updated by Roberto Cirillo almost 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
The problem was due to the persistent folder defined in geoserver/WEB-INF/gcube-app.xml:
<application mode="online">
<name>GeoServer</name>
<group>GeoServer</group>
<version>2.10.3</version>
<persistence location="/srv/geoserver_data"/>
<exclude handlers='request-validation context-retriever'>/*</exclude>
</application>
and this folder is shared with the others geoserver instances.
There'll be not problem if the geoserver is discovered by ServiceEndpoint resource (Gis-GeoServer).
Actions
