A customer indicated that after setting up the read-write they experienced exceptions. During the investigation and discussions we found that in addition to the settings in the official documentation further properties also needs to be applied:
The correct configuration is to set the 'jdbc.default' properties as well as 'jdbc.read' and 'jdbc.write' properties and it should be pointing to the same database as defined in the 'jdbc.write' properties.
The reason for this is that in case the portal.properties settings are used for configuring the database connections, a separated connection pool is used for the Counter table which doesn't use the read/write configuration but the default one. This is because of performance reasons.
Another configuration option is to add the following entry to the portal-ext.properties file:
Please find further information on the following links:
Could this be included in the documentation about how the read-write database configuration can be set up?
Thanks for your help!