[
https://jira.nuxeo.com/browse/NXP-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugen Ionica updated NXP-7498:
------------------------------
Upgrade notes:
for reconnect to database feature the following two lines needs to be uncomment
in $NUXEO_HOME/oracle/deploy/nuxeo-ds.xml
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name-->
( not enabled by default due possible performance issue )
> VCS: cluster node loses identity when connection to database is
> broken/restarted
> --------------------------------------------------------------------------------
>
> Key: NXP-7498
> URL: https://jira.nuxeo.com/browse/NXP-7498
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core SQL Storage
> Affects Versions: 5.4
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Priority: Major
> Fix For: 5.4.3
>
>
> When the connection to the database is broken, there is a mechanism in
> JDBCConnection to attempt to reconnect automatically.
> However if this happens for the cluster connection (first connection), the
> connection will have a new SID (Oracle) / pg_backend_pid (PostgreSQL) which
> won't be added to the CLUSTER_NODES table.
> The effect is that after reconnection the cluster node will not see any
> invalidation from other nodes as they will be sent to a nonexistent node.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
