Hi girls and guys, I'm kind of stuck here.
I wanted to switch to a non-empty postgresql database, containing already
some entries. The contents were inserted by using gn version 3.2.1.
Then I freshly deployed the same gn version, configured first the internal
db (h2) to check if eveything works ok. When I try to connect to postgresql,
this is the output in geonetwork.log :
If I want to switch back do h2.db, the error is still there.
I use externalised datadir. Any sugestions ? Thanks in advance for your
output.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Error-after-switching-DB-node-Invalid-boolean-value-jdbc-basic-defaultReadOnly-tp5327465.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
This is now resolved, but I am not certain about what exactly was the cause.
Below is a conclusion - if any of the developers can confirm that this was
provoking the problem, you're welcome.
In the second configuration the gn_data_dir was, as in the 1st config,
externalised. Besides that schemas were left in their default location, so
CATALINA_OPTS had also the parameter :
/-Dgeonetwork.schema.dir=/app/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins/
This is maybe why the connection back to default H2 node wasn't working
neither. So, I just had to remove the geonetwork.schema.dir part and the
geonetwork page loaded normaly with all the contents from the DB.
This was a test, so no data was lost.
I wrote down some general steps about GN deployment and configuration. I'll
publish it soon, I think it would be useful to have an online reserve plan
for the cases when things don't work as wanted. If anyone will like to
contribute or modify it later on, that would be great too.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Error-after-switching-DB-node-Invalid-boolean-value-jdbc-basic-defaultReadOnly-tp5327465p5327657.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.