...
Note: Run Syncope in real environments is a prerequisite for this page.
OpenJPA Remote Event Notification
When deploying multiple Syncope instances insisting on a single database or database cluster, it is of fundamental importance that the contained OpenJPA instances are correctly configured for remote event notification.
Such configuration, in fact, allows OpenJPA's data cache to remain synchronized when deployed in multiple JVMs, thus enforcing data consistency across all Syncope instances.
The default configuration, in core/src/main/resources/persistenceContextEMFactory.xml is
![]() Code Block |
|
|
<entry key="openjpa.RemoteCommitProvider" value="sjvm"/>
|
which is suited for single JVM installations; with multiple instances, more options like as TCP or JMS are available; see OpenJPA's documentation for reference.
![]() Info |
| OpenJPA documentation refers to direct configuration under META-INF/persistence.xml; for example:
![]() Code Block |
|
|
<property name="openjpa.RemoteCommitProvider" value="jms(ExceptionReconnectAttempts=5)"/>
|
for usage in core/src/main/resources/persistenceContextEMFactory.xml this becomes:
![]() Code Block |
|
|
<entry key="openjpa.RemoteCommitProvider" value="jms(ExceptionReconnectAttempts=5)"/>
|
|
Apache Tomcat 7
Having this as special reference,
...
