[GeoNode-users] Problems setting geofence in cluster
corina_ww at yahoo.com
Tue Oct 17 08:11:27 PDT 2017
Update:After enabling disk quota , I was able to successfully test connection of GeoFence to one of my instances. But still I can not make it work in a cluster. Disk quota doesn't work in cluster too. When trying to enable it on the other GeoServer instance, I receive the following error message:
"Loading quota store failed, the disk quota subsystem is disabled, please re-configure: Could not open JDBC Connection for transaction; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Database may be already in use: Locked by another process. Possible solutions: close all other connection(s); use the server mode [90020-119])
I still don't know what I am missing in the configuration. Any help is much appreciated. :)
On Tuesday, October 17, 2017, 11:41:58 AM GMT+1, Corina Tudorache <corina_ww at yahoo.com> wrote:
I have a working GeoServer 2.10.x in cluster (the version that does include GeoNode) that include two GeoServer istances, for now, and I am trying to get geofence to work with this cluster. Reading the documentation, I understand that I have to make some changes in the file "geofence-server.properties", changing the lines "instanceName=default-gs" "servicesUrl=internal:/ " with the instance name of my cluster and the url that coresponds to my IP (and eventualy the port as well), but it doesn't work.
At first one of my instances worked with the default configuration, this lines "instanceName=default-gs" "servicesUrl=internal:/, when I changed to my cluster name and machine ip, it didn't work . I get the following error message:"org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection"
When I changed the serviceURL to my own IP, it didn't show up in the GeoFence Admin Page. It was still the default option "default-gs".Now it doesn't even work with the default configuration for the instances that used to work at the beginning.
I am missing something with the configuration and I don't know what.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users