January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6050) RemoveExpiredCommand should check the version

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6050?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6050: ------------------------------------ Checking the HotRod version in {{RemoveExpiredCommand}} would fix some of the random failures in the client {{ExpiryTest}}. > RemoveExpiredCommand should check the version > --------------------------------------------- > > Key: ISPN-6050 > URL: https://issues.jboss.org/browse/ISPN-6050 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Fix For: 8.2.0.Alpha1 > > > Cluster-wide expiration is not optional, so it cannot require versioning. But it could and it should use versions when they are present, e.g. with HotRod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6050) RemoveExpiredCommand should check the version

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6050?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-6050: ---------------------------------- Assignee: William Burns > RemoveExpiredCommand should check the version > --------------------------------------------- > > Key: ISPN-6050 > URL: https://issues.jboss.org/browse/ISPN-6050 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 8.2.0.Alpha1 > > > Cluster-wide expiration is not optional, so it cannot require versioning. But it could and it should use versions when they are present, e.g. with HotRod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6050) RemoveExpiredCommand should check the version

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6050: ---------------------------------- Summary: RemoveExpiredCommand should check the version Key: ISPN-6050 URL: https://issues.jboss.org/browse/ISPN-6050 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 8.1.0.Final Reporter: Dan Berindei Fix For: 8.2.0.Alpha1 Cluster-wide expiration is not optional, so it cannot require versioning. But it could and it should use versions when they are present, e.g. with HotRod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5937) HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5937?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5937: ------------------------------- Attachment: ExpiryTest.log.gz > 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 > Labels: testsuite_stability > Fix For: 8.2.0.Alpha1 > > Attachments: ExpiryTest.log.gz > > > 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)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5937) HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5937?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5937: ------------------------------- Status: Open (was: New) > 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 > Labels: testsuite_stability > Fix For: 8.2.0.Alpha1 > > > 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)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5937) HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5937?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5937: ------------------------------------ I have managed to reproduce the test reliably by forcing it to run on a single core ({{taskset -c 1 mvn test -pl client/hotrod-client -Dtest=ExpiryTest}}). There seem to be 2 problems: 1. {{RemoveExpiredCommand}} only knows the key, the value, and the lifespan. Since all test methods use the same keys and values, and the default lifespan, then a delayed {{RemoveExpiredCommand}} deleting a newer value is a limitation that was known when Will started implementing cluster-wide expiration. On the other hand, HotRod uses versions, so {{RemoveExpiredCommand}} should also check the versions to make sure it's removing the correct value. 2. {{ClusterExpirationManager}} doesn't always create the {{RemoveExpiredCommand}} with the proper value, because {{ClusterExpirationManager.handleLifespanExpired}} doesn't lock the entry and the value is actually read in the async thread. This allows another thread to modify the value in the data container *and* in the entry that was passed to the async thread, before the {{RemoveExpiredCommand}} was created. > 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 > Labels: testsuite_stability > Fix For: 8.2.0.Alpha1 > > > 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)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; need to be run in privileged block

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6049?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-6049: --------------------------------- Description: Problematic are the calls that are originating in the unprivileged user code. For example: org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata e.g. call stack https://gist.github.com/rhusar/e2ae371f852d926c5e13 was: Problematic are the calls that are originating in the unprivileged user code. For example: org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata > Calls to reflection API fail with enabled security manager; need to be run in privileged block > ---------------------------------------------------------------------------------------------- > > Key: ISPN-6049 > URL: https://issues.jboss.org/browse/ISPN-6049 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Problematic are the calls that are originating in the unprivileged user code. For example: > org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup > org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata > e.g. call stack https://gist.github.com/rhusar/e2ae371f852d926c5e13 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; need to be run in privileged block

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6049?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-6049: --------------------------------- Description: Problematic are the calls that are originating in the unprivileged user code. For example: org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata was: Problematic are the calls that are originating in unprivileged user code. E.g. org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata > Calls to reflection API fail with enabled security manager; need to be run in privileged block > ---------------------------------------------------------------------------------------------- > > Key: ISPN-6049 > URL: https://issues.jboss.org/browse/ISPN-6049 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Problematic are the calls that are originating in the unprivileged user code. For example: > org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup > org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; needs to be run in privileged block

by Radoslav Husar (JIRA)

Radoslav Husar created ISPN-6049: ------------------------------------ Summary: Calls to reflection API fail with enabled security manager; needs to be run in privileged block Key: ISPN-6049 URL: https://issues.jboss.org/browse/ISPN-6049 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.1.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Problematic are the calls that are originating in unprivileged user code. E.g. org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6049) Calls to reflection API fail with enabled security manager; need to be run in privileged block

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-6049?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-6049: --------------------------------- Summary: Calls to reflection API fail with enabled security manager; need to be run in privileged block (was: Calls to reflection API fail with enabled security manager; needs to be run in privileged block) > Calls to reflection API fail with enabled security manager; need to be run in privileged block > ---------------------------------------------------------------------------------------------- > > Key: ISPN-6049 > URL: https://issues.jboss.org/browse/ISPN-6049 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Problematic are the calls that are originating in unprivileged user code. > E.g. > org.infinispan.distribution.group.GroupManagerImpl.GroupMetadataImpl#getGroup > org.infinispan.distribution.group.GroupManagerImpl#createGroupMetadata -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016