January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4604) Race condition in the QueryInterceptor involving SearchFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4604?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4604: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1139669|https://bugzilla.redhat.com/show_bug.cgi?id=1139669] from VERIFIED to CLOSED > Race condition in the QueryInterceptor involving SearchFactory > -------------------------------------------------------------- > > Key: ISPN-4604 > URL: https://issues.jboss.org/browse/ISPN-4604 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Test Suite - Query > Affects Versions: 7.0.0.Alpha5 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta1 > > > During perform work task in the QueryInterceptor, the underlying SearchFactory could be swapped (for example by some other thread calling SearchFactory.addClass) and temporarily return null when looking for indexBindings, and throws intermittent Exceptions like: > {code} > Caused by: org.hibernate.search.exception.SearchException: Unable to perform work. Entity Class is not @Indexed nor hosts @ContainedIn: class org.infinispan.query.test.VeryLongIndexNamedClass > at org.hibernate.search.backend.impl.TransactionalWorker.performWork(TransactionalWorker.java:58) > at org.infinispan.query.backend.QueryInterceptor.performSearchWorks(QueryInterceptor.java:233) > at org.infinispan.query.backend.QueryInterceptor.performSearchWork(QueryInterceptor.java:227) > at org.infinispan.query.backend.QueryInterceptor.updateIndexes(QueryInterceptor.java:221) > at org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(QueryInterceptor.java:531) > at org.infinispan.query.backend.QueryInterceptor.visitPutKeyValueCommand(QueryInterceptor.java:162) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:71) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitPutKeyValueCommand(AbstractLockingInterceptor.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4029) NotifyingFutureTest.testExceptionOtherThread1 && testDoneOtherThread2 random failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4029?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4029: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1074457|https://bugzilla.redhat.com/show_bug.cgi?id=1074457] from VERIFIED to CLOSED > NotifyingFutureTest.testExceptionOtherThread1 && testDoneOtherThread2 random failures > ------------------------------------------------------------------------------------- > > Key: ISPN-4029 > URL: https://issues.jboss.org/browse/ISPN-4029 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Labels: testsuite_stability > Fix For: 7.0.0.Final > > > {noformat} > 16:58:33,402 ERROR (testng-NotifyingFutureTest:) [UnitTestTestNGListener] Test testExceptionOtherThread1(org.infinispan.commons.util.concurrent.NotifyingFutureTest) failed. > java.lang.AssertionError: expected [true] but found [false] > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotEquals(Assert.java:494) > at org.testng.Assert.assertTrue(Assert.java:42) > at org.testng.Assert.assertTrue(Assert.java:52) > at org.infinispan.commons.util.concurrent.NotifyingFutureTest.testException(NotifyingFutureTest.java:150) > at org.infinispan.commons.util.concurrent.NotifyingFutureTest.testExceptionOtherThread(NotifyingFutureTest.java:67) > at org.infinispan.commons.util.concurrent.NotifyingFutureTest.testExceptionOtherThread1(NotifyingFutureTest.java:46) > {noformat} > The test submits a task to a ThreadPoolExecutor that notifies a NotifyingFutureImpl and assumes that when the NotifyingFutureImpl is done, the original Future is also done. That's clearly not happening some of the time. > * Jenkins > ** RHEL, Oracle JDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > ** RHEL, OpenJDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4871) Remove KeyValueFilterFactory and ConverterFactory to prevent confusion

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4871?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4871: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1154044|https://bugzilla.redhat.com/show_bug.cgi?id=1154044] from VERIFIED to CLOSED > Remove KeyValueFilterFactory and ConverterFactory to prevent confusion > ---------------------------------------------------------------------- > > Key: ISPN-4871 > URL: https://issues.jboss.org/browse/ISPN-4871 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 7.0.0.CR2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > When ISPN-4753 was added we moved to CacheEventFilterFactory and CacheEventConverterFactory. Thinking about this more it is confusing to have both factories when the one is not used currently. We should remove it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4850) Allow for filter and conversion to be done in one step for cache listeners

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4850?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4850: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1154044|https://bugzilla.redhat.com/show_bug.cgi?id=1154044] from VERIFIED to CLOSED > Allow for filter and conversion to be done in one step for cache listeners > -------------------------------------------------------------------------- > > Key: ISPN-4850 > URL: https://issues.jboss.org/browse/ISPN-4850 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.CR1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > Currently the cache listeners can install a CacheEventFilter and CacheEventConverter to be used. However each one requires separate invocations. It would be desireable to have this done as a single invocation akin to what we did for ISPN-4640. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4792) RemoteClusterListener still invokes filter/converter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4792?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4792: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1154044|https://bugzilla.redhat.com/show_bug.cgi?id=1154044] from VERIFIED to CLOSED > RemoteClusterListener still invokes filter/converter > ---------------------------------------------------- > > Key: ISPN-4792 > URL: https://issues.jboss.org/browse/ISPN-4792 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR1 > > > When using a distributed cluster listener it installs a listener on each of the nodes to receive notifications. Cluster listeners only raise post events, but on remote nodes (ones where the listener wasn't originally installed) they invoke the filter and converter even on pre events which is not needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4944) Improve HR client security test coverage

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4944?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4944: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1167678|https://bugzilla.redhat.com/show_bug.cgi?id=1167678] from VERIFIED to CLOSED > Improve HR client security test coverage > ---------------------------------------- > > Key: ISPN-4944 > URL: https://issues.jboss.org/browse/ISPN-4944 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.1.0.Alpha1, 7.1.0.Final > > > Extends security test for HR client so that the tests cover all HR operations (available on [Remote cache|https://docs.jboss.org/infinispan/7.0/apidocs/org/infinispan/client...]) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4707) On leave, Hot Rod client ends up with old cluster formation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4707?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4707: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1140123|https://bugzilla.redhat.com/show_bug.cgi?id=1140123] from VERIFIED to CLOSED > On leave, Hot Rod client ends up with old cluster formation > ----------------------------------------------------------- > > Key: ISPN-4707 > URL: https://issues.jboss.org/browse/ISPN-4707 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.CR1 > > Attachments: hr-protocol-13.log, hr-protocol-20.log > > > In spite of that, at least with version 2.0 of the protocol, the consistent hash works fine and sends requests to remaining nodes only, without failure. On version 1.3 of the protocol, the cluster formation is updated correctly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5111) [CLI] HELP of container command should be changed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5111?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5111: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 961317|https://bugzilla.redhat.com/show_bug.cgi?id=961317] from VERIFIED to CLOSED > [CLI] HELP of container command should be changed > ------------------------------------------------- > > Key: ISPN-5111 > URL: https://issues.jboss.org/browse/ISPN-5111 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.0.Alpha1 > Reporter: Vitalii Chepeliuk > Assignee: Vitalii Chepeliuk > Priority: Minor > Fix For: 7.1.0.CR2 > > > CONTAINER COMMAND--------------------------------------------------------------- > SYNOPSIS > container [containername] > > DESCRIPTION > Shows the available containers or selects a container to be used as default for CLI operations > > ARGUMENTS > <<cachename>> !!! should be "containername" > (optional) the name of the container to set as default for the following operations -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3087) [CLI] HELP of some commands should to be changed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3087?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3087: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 961317|https://bugzilla.redhat.com/show_bug.cgi?id=961317] from VERIFIED to CLOSED > [CLI] HELP of some commands should to be changed > ------------------------------------------------ > > Key: ISPN-3087 > URL: https://issues.jboss.org/browse/ISPN-3087 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.4.Final > Environment: ALL > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Labels: cli > Fix For: 5.3.0.CR2 > > > Description of problem: > Grammar mistakes in help of begin, connect, container, locate, put, replace, stats, upgrade commands should be fixed. Wrong words are wrapped in <<wrong word>> > BEGIN COMMAND-------------------------------------------------------------------- > SYNOPSIS > begin [cachename] > > DESCRIPTION > Starts a transaction > > ARGUMENTS > cachename > (optional) the name of the cache on which to start the transaction. The currently selected cache will be used if this argument is <<missingThe>> cache must be transactional for > this command to work > CONNECT COMMAND------------------------------------------------------------------ > SYNOPSIS > connect protocol://[user[:password]@]host][:port][/container[/cache]] > > DESCRIPTION > Connects to an Infinispan instance using the specified protocol, host and port and with the supplied credentials. > > ARGUMENTS > protocol > currently only the jmx and the remoting (JMX over JBoss Remoting) protocols are supported. The jmxprotocol should be used to connect to directly over the standard JMX > protocol, whereas <<theremotingprotocol>> should be used to connect to an Infinispan instance managed within an AS/EAP/JDG-style container. > user (optional) > The username to use when connecting if the server requires credentials > password (optional) > The password to use when connecting if the server requires credentials. When omitted, the password will be asked for interactively > host > the host name or IP address where the Infinispan instance is running > port > the port to connect to. For <<theremotingprotocol>> this defaults to 9999 > container (optional) > the cache container to connect to by default. If unspecified, the first cache container will be selected > cache (optional) > the cache to connect to by default. If unspecified, no cache will be selected > CONTAINER COMMAND--------------------------------------------------------------- > SYNOPSIS > container [containername] > > DESCRIPTION > Shows the available containers or selects a container to be used as default for CLI operations > > ARGUMENTS > <<cachename>> > (optional) the name of the container to set as default for the following operations > LOCATE COMMAND------------------------------------------------------------------ > SYNOPSIS > locate [--codec=codec] [cache.]key > > DESCRIPTION > Shows the addresses of the owners in the cluster of the entry associated with the specified key. This command <<onlyworks>> for distributed caches > > ARGUMENTS > cache > (optional) the name of the cache to use. If not specified, the currently selected cache will be used. See the cache command > key the key of the entry for which to show the address--codec=codec option has been specified then the key will be encoded using the specified codec, otherwise the default > session codec will be used. See <<theencoding>> command for more information > PUT COMMAND--------------------------------------------------------------------- > SYNOPSIS > put [--codec=codec] [--ifabsent] [cache.]key value [expires expiration [maxidle idletime]] > > DESCRIPTION > Associates the specified value with the specified key in this cache. If the cache previously contained a mapping for the key, the old value is replaced by the specified value. > Optionally allows setting of a lifespan and a maximum idle time. > > ARGUMENTS > cache > the name of the cache where the key/value pair will be stored. If omitted uses the currently selected cache (see the <<cachecommand>>) > key the key which identifies the element in the cache > value > the value to store in the cache associated with the keyIf the --codec=<<codecoption>> has been specified then the key and value will be encoded using the specified codec, > otherwise the default session codec will be used. See <<theencodingcommand>> for more information > expiration > an optional expiration timeout (using the time value notation described below) > idletime > an optional idle timeout (using the time value notation described below) > > DATA TYPES > The CLI understands the following types: > string > strings can either be quoted between single (') or double (") quotes, or left unquoted. In this case it must not contain spaces, punctuation and cannot begin with a number > e.g. 'a string', key001 > int an integer is identified by a sequence of decimal digits, e.g. 256 > long > a long is identified by a sequence of decimal digits suffixed by 'l', e.g. 1000l > double > a double precision number is identified by a floating point number(with optional exponent part) and an optional 'd' suffix, e.g.3.14 > float > a single precision number is identified by a floating point number(with optional exponent part) and an 'f' suffix, e.g. 10.3f > boolean > a boolean is represented either by the keywords true and false > UUID > a UUID is represented by its canonical form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX > JSON > serialized Java classes can be represented using JSON notation, e.g. {"package.MyClass":{"i":5,"x":null,"b":true}}. Please note that the specified class must be available to > the CacheManager's class loader. > > TIME VALUES > A time value is an integer number followed by time unit suffix: days (d), hours (h), minutes (m), seconds (s), milliseconds (ms) > REPLACE COMMAND----------------------------------------------------------------- > See put command above > UPGRADE COMMAND----------------------------------------------------------------- > SYNOPSIS > upgrade [--dumpkeys | --synchronize=migrator | --disconnectsource=migrator] [cachename | --all] > > DESCRIPTION > This command performs operations used during the rolling upgrade procedure. > > ARGUMENTS > --dumpkeys > Performs the dump of all the keys in the cache to a known entry. It must be performed on the "source" cluster so that the "target" cluster can fetch the entire keyset > efficiently to complete the synchronization operation > --synchronize=migrator > Performs the synchronization of all data from the "source" cluster to the "target" cluster using the specified migrator. It must be performed on the "target" cluster after > the --dumpkeys operation has been performed on the "source" cluster. The only migrator currently available is hotrod which migrates entries between caches exposed via the > HotRod remoting protocol. > --disconnectsource=migrator > Disconnects the "target" cluster from the "source" cluster. This is performed in a migrator-specific way. After this operation has been performed the "source" cluster can be > switched off > --all > Specifies that the requested operation should be performed on all caches in the currently selected container > cachename > (optional) the name of the cache on which to invoke the specified upgrade command. If unspecified, the currently selected cache will be used. See also the --all switch above > > USAGE > In order to perform a rolling upgrade of a HotRod cluster, the following steps must be taken > 1. Configure and start a new cluster with a RemoteCacheStore pointing to the old cluster and the > hotRodWrapping flag enabled > 2. Configure all clients so that they will connect to the new cluster > <<some space alignment needed here on 3. >> > 3. Invoke the > upgrade --dumpkeys command on the old cluster for all of the caches that need to be migrated > 4. Invoke the > upgrade --synchronize=hotrod command on the new cluster to ensure that all data is migrated from the old cluster to the new one > 5. Invoke the > upgrade --disconnectsource=hotrod command on the new cluster to disable the RemoteCacheStore used to migrate the data > 6. Switch off the old cluster > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4753) Add oldValue, oldMetadata and retry flag to filter and converter for Cluster Listeners.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4753?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4753: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1150232|https://bugzilla.redhat.com/show_bug.cgi?id=1150232] from VERIFIED to CLOSED > Add oldValue, oldMetadata and retry flag to filter and converter for Cluster Listeners. > --------------------------------------------------------------------------------------- > > Key: ISPN-4753 > URL: https://issues.jboss.org/browse/ISPN-4753 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR1 > > > It has been brought up that the filter and converter provided for use with Cluster Listeners need to also have access to the previous value/metadata and if the operation was a retry operation to allow for proper behavior of continuous query and other types of implementations. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015