[JBoss JIRA] (ISPN-5863) Default metadata not merged for DecoratedCache operations
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5863:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1272052|https://bugzilla.redhat.com/show_bug.cgi?id=1272052] from NEW to ASSIGNED
> Default metadata not merged for DecoratedCache operations
> ---------------------------------------------------------
>
> Key: ISPN-5863
> URL: https://issues.jboss.org/browse/ISPN-5863
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta1
>
>
> If the ISPN server cache is configured with expiration like:
> <cache-container name="local" default-cache="default" statistics="true">
> <state-persistence/>
> <local-cache name="default" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <expiration lifespan="1000" interval="20000"/>
> </local-cache>
> The entry should automatic expired in 1second after it is added.
> But a client still have the key
> - after 1 sec where it should have been expired
> - after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5623) Retried prepare commands do not wait for backup locks
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5623?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5623:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1245500|https://bugzilla.redhat.com/show_bug.cgi?id=1245500] from NEW to ASSIGNED
> Retried prepare commands do not wait for backup locks
> -----------------------------------------------------
>
> Key: ISPN-5623
> URL: https://issues.jboss.org/browse/ISPN-5623
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.2.3.Final, 8.0.0.Beta1
> Reporter: Dan Berindei
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 8.1.0.Final
>
> Attachments: OptimisticPrimaryOwnerCrashDuringPrepareTest.java
>
>
> When the primary owner crashes during prepare, the prepare command is retried on the new primary owner. But because the transaction topology id stays the same, the new primary owner does not check for backup locks owned by other transactions from the previous topology.
> That makes it possible for the retried prepare command to lock a key that was already locked by another transaction on the primary owner.
> This wasn't a problem before the ISPN-4546 fix, because a primary owner crash would have forced the transaction to roll back.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5912) Sync Infinispan components branches from Camel upstream.
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-5912:
----------------------------------
Summary: Sync Infinispan components branches from Camel upstream.
Key: ISPN-5912
URL: https://issues.jboss.org/browse/ISPN-5912
Project: Infinispan
Issue Type: Task
Components: Core
Reporter: Pedro Zapata
The Infinispan component was forked for the Camel component, and both branches have diverged since. Changes upstream need to tracked down and backported. Then, a pull-request need to be issued upstream to sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months