January 2016 - infinispan-issues - Jboss List Archives

[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 reassigned ISPN-5937: ---------------------------------- Assignee: Martin Vrabel > 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 > Assignee: Martin Vrabel > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5727) Client Listener removal and shutdown problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5727?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5727: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1297930|https://bugzilla.redhat.com/show_bug.cgi?id=1297930] from POST to MODIFIED > Client Listener removal and shutdown problems > --------------------------------------------- > > Key: ISPN-5727 > URL: https://issues.jboss.org/browse/ISPN-5727 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final, 8.0.2.Final > > > There are a couple of problems related to client listener registration on the client: > 1. When shutting down a remote cache manager to which client listeners have been added, even if the user does not remove them individually, stopping the remote cache manager should shutdown all client-side client listener threads. This is not the case right now. > 2. When removing a client listener, the client listener thread needs to be stopped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1518) Log the Infinispan version information once

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-1518?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1518: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Log the Infinispan version information once > ------------------------------------------- > > Key: ISPN-1518 > URL: https://issues.jboss.org/browse/ISPN-1518 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.1.0.BETA4 > Reporter: Randall Hauch > Assignee: Paul Ferraro > Priority: Minor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > When running unit tests for a system that uses Infinispan, the log is filled with the following messages: > {code} > INFO ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA4 > {code} > It looks like this may be logged each time an Infinispan cache manager is instantiated, but it would be really nice if this were done only once, perhaps in a static initializer for one of the classes. This would likely mean little change for production systems. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1518) Log the Infinispan version information once

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-1518?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-1518: ------------------------------- Fix Version/s: 8.2.0.Alpha1 8.1.1.Final > Log the Infinispan version information once > ------------------------------------------- > > Key: ISPN-1518 > URL: https://issues.jboss.org/browse/ISPN-1518 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.1.0.BETA4 > Reporter: Randall Hauch > Assignee: Paul Ferraro > Priority: Minor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > When running unit tests for a system that uses Infinispan, the log is filled with the following messages: > {code} > INFO ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA4 > {code} > It looks like this may be logged each time an Infinispan cache manager is instantiated, but it would be really nice if this were done only once, perhaps in a static initializer for one of the classes. This would likely mean little change for production systems. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1518) Log the Infinispan version information once

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-1518?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-1518: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/3939, https://github.com/infinispan/infinispan/pull/3940 (was: https://github.com/infinispan/infinispan/pull/637) > Log the Infinispan version information once > ------------------------------------------- > > Key: ISPN-1518 > URL: https://issues.jboss.org/browse/ISPN-1518 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.1.0.BETA4 > Reporter: Randall Hauch > Assignee: Paul Ferraro > Priority: Minor > > When running unit tests for a system that uses Infinispan, the log is filled with the following messages: > {code} > INFO ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA4 > {code} > It looks like this may be logged each time an Infinispan cache manager is instantiated, but it would be really nice if this were done only once, perhaps in a static initializer for one of the classes. This would likely mean little change for production systems. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1518) Log the Infinispan version information once

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-1518?page=com.atlassian.jira.plugin.... ] Paul Ferraro reopened ISPN-1518: -------------------------------- Assignee: Paul Ferraro (was: Manik Surtani) Implemented fix can still log multiple times for multiple simultaneously started cache managers. > Log the Infinispan version information once > ------------------------------------------- > > Key: ISPN-1518 > URL: https://issues.jboss.org/browse/ISPN-1518 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.1.0.BETA4 > Reporter: Randall Hauch > Assignee: Paul Ferraro > Priority: Minor > > When running unit tests for a system that uses Infinispan, the log is filled with the following messages: > {code} > INFO ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.BETA4 > {code} > It looks like this may be logged each time an Infinispan cache manager is instantiated, but it would be really nice if this were done only once, perhaps in a static initializer for one of the classes. This would likely mean little change for production systems. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6078) Collect events from all nodes using distexec

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6078?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6078: ---------------------------------- Fix Version/s: 8.2.0.Final > Collect events from all nodes using distexec > -------------------------------------------- > > Key: ISPN-6078 > URL: https://issues.jboss.org/browse/ISPN-6078 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Final > > > Once the distexec api can run without a distcache, we need to collect all events, sort them and filter them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6078) Collect events from all nodes using distexec

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6078: ------------------------------------- Summary: Collect events from all nodes using distexec Key: ISPN-6078 URL: https://issues.jboss.org/browse/ISPN-6078 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Once the distexec api can run without a distcache, we need to collect all events, sort them and filter them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6078) Collect events from all nodes using distexec

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6078?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6078: ------------------------------------- Assignee: Tristan Tarrant > Collect events from all nodes using distexec > -------------------------------------------- > > Key: ISPN-6078 > URL: https://issues.jboss.org/browse/ISPN-6078 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Once the distexec api can run without a distcache, we need to collect all events, sort them and filter them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5988) Fine-/Coarse-grained AtomicMap info is not preserved in cache

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5988?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5988: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fine-/Coarse-grained AtomicMap info is not preserved in cache > ------------------------------------------------------------- > > Key: ISPN-5988 > URL: https://issues.jboss.org/browse/ISPN-5988 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Pedro Ruivo > Fix For: 8.2.0.Alpha1 > > > In `AtomicMapAPITest#testAtomicMapAfterFineGrainedAtomicMap` we test that one entry cannot be mapped to both fine- and coarse-grained atomic map. However, the test relies on local node being owner, because the check is based on type of the proxy - but the proxy is not persisted in cache. > So in practice you can access the fine-grained map as coarse-grained and vice versa. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016