[JBoss JIRA] (ISPN-5623) Retried prepare commands do not wait for backup locks
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5623?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5623:
------------------------------
Status: Open (was: New)
> 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
> 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-5937) HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-5937:
----------------------------------
Summary: HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures
Key: ISPN-5937
URL: https://issues.jboss.org/browse/ISPN-5937
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 8.1.0.Beta1
Reporter: Dan Berindei
Priority: Critical
Fix For: 8.1.0.Beta2
The put operation succeeds, but the get immediately afterwards doesn't find the entry:
{noformat}
java.lang.AssertionError: expected:<v1> but was:<null>
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108)
at org.infinispan.client.hotrod.ExpiryTest.expectCachedThenExpired(ExpiryTest.java:103)
at org.infinispan.client.hotrod.ExpiryTest.expectExpiryAfterRequest(ExpiryTest.java:99)
at org.infinispan.client.hotrod.ExpiryTest.testGlobalExpiryPutWithFlag(ExpiryTest.java:46){noformat}
http://ci.infinispan.org/viewLog.html?buildId=31770&tab=buildResultsDiv&b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5923) Wrong results when applying the <= operator to a string attribute having a null token defined
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5923?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-5923:
--------------------------------
Fix Version/s: 8.1.0.Beta2
(was: 8.1.0.Beta1)
> Wrong results when applying the <= operator to a string attribute having a null token defined
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-5923
> URL: https://issues.jboss.org/browse/ISPN-5923
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta2, 8.0.2.Final
>
>
> The query having("myField").lte("Something") gets translated to lucene as myField:['_null_' TO 'Something'] where _null_ is the defined null token for this field. This query returns wrong results or no results at all, depending on the value of the null token. The issue no longer appears if there is no null token defined; it will get properly translated to myField:[* TO 'Something'] .
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months