January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3932) FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3932?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3932: ----------------------------------------------- Pedro Ruivo <pruivo(a)redhat.com> changed the Status of [bug 1047905|https://bugzilla.redhat.com/show_bug.cgi?id=1047905] from NEW to POST > FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions > ------------------------------------------------------------------------------------ > > Key: ISPN-3932 > URL: https://issues.jboss.org/browse/ISPN-3932 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.7.Final, 6.0.1.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > FineGrainedAtomicMap doesn't respect the REPEATABLE_READ isolation level: a transaction holding a FGAM reference will see subkeys added by another concurrent transaction. > A test with PESSIMISTIC locking is here: https://github.com/danberindei/infinispan/commit/526ae4c414009b2a95b39a65... > We need to test OPTIMISTIC locking and the coarse-grained AtomicMap as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3951) Make sure TestingUtil.replaceComponent is only called after mock is fully configured

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3951?page=com.atlassian.jira.plugin.... ] Work on ISPN-3951 started by William Burns. > Make sure TestingUtil.replaceComponent is only called after mock is fully configured > ------------------------------------------------------------------------------------ > > Key: ISPN-3951 > URL: https://issues.jboss.org/browse/ISPN-3951 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Some of our tests replace existing components. Unfortunately these could be replaced with mocks that aren't fully initialized until the next line. This can cause spurious test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3951) Make sure TestingUtil.replaceComponent is only called after mock is fully configured

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3951?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-3951: ----------------------------------- Assignee: William Burns (was: Dan Berindei) > Make sure TestingUtil.replaceComponent is only called after mock is fully configured > ------------------------------------------------------------------------------------ > > Key: ISPN-3951 > URL: https://issues.jboss.org/browse/ISPN-3951 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Some of our tests replace existing components. Unfortunately these could be replaced with mocks that aren't fully initialized until the next line. This can cause spurious test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3951) Make sure TestingUtil.replaceComponent is only called after mock is fully configured

by William Burns (JIRA)

William Burns created ISPN-3951: ----------------------------------- Summary: Make sure TestingUtil.replaceComponent is only called after mock is fully configured Key: ISPN-3951 URL: https://issues.jboss.org/browse/ISPN-3951 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 6.0.0.Final Reporter: William Burns Assignee: Dan Berindei Fix For: 7.0.0.Alpha1, 7.0.0.Final Some of our tests replace existing components. Unfortunately these could be replaced with mocks that aren't fully initialized until the next line. This can cause spurious test failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3932) FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3932?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3932: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions > ------------------------------------------------------------------------------------ > > Key: ISPN-3932 > URL: https://issues.jboss.org/browse/ISPN-3932 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.7.Final, 6.0.1.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > FineGrainedAtomicMap doesn't respect the REPEATABLE_READ isolation level: a transaction holding a FGAM reference will see subkeys added by another concurrent transaction. > A test with PESSIMISTIC locking is here: https://github.com/danberindei/infinispan/commit/526ae4c414009b2a95b39a65... > We need to test OPTIMISTIC locking and the coarse-grained AtomicMap as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3942: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059277 > HotRod client keep trying recover a connection to a cluster member after shutdown > --------------------------------------------------------------------------------- > > Key: ISPN-3942 > URL: https://issues.jboss.org/browse/ISPN-3942 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Infinispan server with HotRod client in server-client mode and replicated caches. > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Labels: clustered, hotrod, hotrod-java-client > Attachments: hotrod-client.log > > > If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. > There is only a replicated cache configured. > From the server-logfile the new cluster view is established > 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] > There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. > This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3950) Deploy user-code to Infinispan server

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3950: ------------------------------------- Summary: Deploy user-code to Infinispan server Key: ISPN-3950 URL: https://issues.jboss.org/browse/ISPN-3950 Project: Infinispan Issue Type: Feature Request Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Infinispan Server should allow deploying JARs which follow the standard Java service provider API. Support: groupers, listeners, map/reduce jobs, distexec jobs, interceptors, JPA entities, etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3932) FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3932?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3932: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/2355, https://github.com/infinispan/infinispan/pull/2357 (was: https://github.com/infinispan/infinispan/pull/2355) > FineGrainedAtomicMap with REPEATABLE_READ sees modifications from other transactions > ------------------------------------------------------------------------------------ > > Key: ISPN-3932 > URL: https://issues.jboss.org/browse/ISPN-3932 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.2.7.Final, 6.0.1.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > FineGrainedAtomicMap doesn't respect the REPEATABLE_READ isolation level: a transaction holding a FGAM reference will see subkeys added by another concurrent transaction. > A test with PESSIMISTIC locking is here: https://github.com/danberindei/infinispan/commit/526ae4c414009b2a95b39a65... > We need to test OPTIMISTIC locking and the coarse-grained AtomicMap as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3949) Support querying on simple values

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3949: ------------------------------------- Summary: Support querying on simple values Key: ISPN-3949 URL: https://issues.jboss.org/browse/ISPN-3949 Project: Infinispan Issue Type: Feature Request Components: Embedded Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 7.0.0.Final Ironically while we support searching on rich domain objects, we don't allow running queries on the most simple types which users could store in the grid: Strings, Numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3944) DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3944?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3944: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures > ---------------------------------------------------------------------------------------- > > Key: ISPN-3944 > URL: https://issues.jboss.org/browse/ISPN-3944 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: William Burns > Labels: testsuite_stability > Fix For: 7.0.0.Final > > Attachments: dsl1rrft.log.gz > > > Random failure in DistSyncL1RepeatableReadFuncTest>DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace: > {noformat} > 00:23:34,658 ERROR (testng-DistSyncL1RepeatableReadFuncTest:) [UnitTestTestNGListener] Test testNoEntryInL1GetWithConcurrentReplace(org.infinispan.distribution.DistSyncL1RepeatableReadFuncTest) failed. > java.lang.AssertionError: Entry for key [key-to-the-cache] should be in L1 on cache at [NodeA-57647]! > at org.infinispan.distribution.DistributionTestHelper.assertIsInL1(DistributionTestHelper.java:31) > at org.infinispan.distribution.BaseDistFunctionalTest.assertIsInL1(BaseDistFunctionalTest.java:183) > at org.infinispan.distribution.DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace(DistSyncL1FuncTest.java:193) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2014