[JBoss JIRA] (ISPN-7144) Cross-Site Replication: inconsistent data with multiple site masters
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7144?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7144:
------------------------------
Fix Version/s: 9.0.1.Final
> Cross-Site Replication: inconsistent data with multiple site masters
> --------------------------------------------------------------------
>
> Key: ISPN-7144
> URL: https://issues.jboss.org/browse/ISPN-7144
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.0.0.Alpha4
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 9.0.1.Final
>
>
> Cross-Site replication with multiple site masters may not work properly when configured asynchronously.
> It relies on the deliver order of the updates to the remote site but, with multiple site masters, it is possible an update to go through one of the possible routes. Having commands going through different routes violates the FIFO order needed leading to inconsistent data between sites.
> Note: it doesn't happen in synchronous mode.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (ISPN-7144) Cross-Site Replication: inconsistent data with multiple site masters
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7144?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7144:
------------------------------
Status: Open (was: New)
> Cross-Site Replication: inconsistent data with multiple site masters
> --------------------------------------------------------------------
>
> Key: ISPN-7144
> URL: https://issues.jboss.org/browse/ISPN-7144
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 9.0.0.Alpha4
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
>
> Cross-Site replication with multiple site masters may not work properly when configured asynchronously.
> It relies on the deliver order of the updates to the remote site but, with multiple site masters, it is possible an update to go through one of the possible routes. Having commands going through different routes violates the FIFO order needed leading to inconsistent data between sites.
> Note: it doesn't happen in synchronous mode.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (ISPN-7704) AbstractFileLookup#lookupFileStrict should also support absolute paths
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7704?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7704:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.1.Final
Resolution: Done
> AbstractFileLookup#lookupFileStrict should also support absolute paths
> ----------------------------------------------------------------------
>
> Key: ISPN-7704
> URL: https://issues.jboss.org/browse/ISPN-7704
> Project: Infinispan
> Issue Type: Bug
> Components: JCache, Spring Integration
> Affects Versions: 9.0.0.Final
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Fix For: 9.0.1.Final
>
>
> When specifying {{spring.cache.jcache.config}} value in Spring's application.properties, Spring passes us a scheme with absolute path (e.g. {{file:/home/slaskawi/work/infinispan/CacheTest/target/classes/infinispan.xml}}). This causes problems with {{AbstractFileLookup#lookupFileStrict(java.net.URI, java.lang.ClassLoader)}} since it should construct a new {{File}} rather than load this resource from the classloader.
> Related Pull Request: https://github.com/infinispan/infinispan/pull/4474
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months