January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4077) Infinispan REST server welcome page has links to old documetation pages

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4077?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4077: ------------------------------------- Assignee: Tristan Tarrant (was: Adrian Nistor) > Infinispan REST server welcome page has links to old documetation pages > ----------------------------------------------------------------------- > > Key: ISPN-4077 > URL: https://issues.jboss.org/browse/ISPN-4077 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Server > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 7.1.0.CR1 > > > Links to old CMS should be switched towards the new infinispan.org. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3843: ------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4359) Provide an annotation driven way of declaring protobuf metadata

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4359?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4359: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1172646|https://bugzilla.redhat.com/show_bug.cgi?id=1172646] from ON_QA to VERIFIED > Provide an annotation driven way of declaring protobuf metadata > --------------------------------------------------------------- > > Key: ISPN-4359 > URL: https://issues.jboss.org/browse/ISPN-4359 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Affects Versions: 7.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > Fix For: 7.1.0.Beta1 > > > The main goal of this is to simply marshalling of java objects to protobuf using the Protostream library. > Instead of providing a Protostream MessageMarshaller implementation and a proto schema file it would be nice to have an alternative way of just adding minimal annotations to a Java class (and its fields) to assist on the fly generation (via reflection) of the proto schema. The Protostream library should also infer the marshaller so it would not require a manually implemented one. The annotation should require minimal info (tag number) and the rest should be inferred based on common sense defaults (protobuf type, java collection type, collection element type ...) but should be possible to override. The auto-generated schema should be available to users and they should be able then to use it as reference if they need it to implement domain model classes and marshallers for other languages. > The user should still be able to specify a manually created schema (besides the annotated classes) and in that case the Protostream library should check the auto-inferred schema against the provided one and ensure they match. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3843) Remove broadcast/unicast optimization in JGroupsTransport

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3843?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3843: ------------------------------------ It's probably not that important, as messages from different senders are not ordered anyway (either by UNICAST3 or NAKACK2). In asynchronous non-tx caches updates for the same key are ordered because they are all sent from the primary owner, but the primary owner will also change for at least some of the keys when the cluster size changes. > Remove broadcast/unicast optimization in JGroupsTransport > --------------------------------------------------------- > > Key: ISPN-3843 > URL: https://issues.jboss.org/browse/ISPN-3843 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Fix For: 7.1.0.CR1 > > > The broadcast/unicast optimization in JGroupsTransport can break the message ordering for regular messages, because NAKACK[2] and UNICAST[2|3] have their own ordering. > We should test if this optimization really brings any performance benefits and eliminate it, at least for asynchronous commands. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4088) Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4088?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4088: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-4088 > URL: https://issues.jboss.org/browse/ISPN-4088 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 64QueryBlockers > > The method exists in both new DSL and the classic query api. > It should be clarified whether this method and the related pagination methods should use int or long for specifying offsets within the data, also should decide if the total number of results / results per page is a long or an int - and update all involved method signatures to have a unitary treatment of this issue. > It appears that recent Lucene versions can offer the number of results as long, while older ones offer it as int (should be verified). > This issue was raised in a github conversation here: https://github.com/infinispan/infinispan/pull/2410 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4088) Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4088?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-4088: --------------------------------------- This would break API. It will need to be postponed to 8.0 > Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-4088 > URL: https://issues.jboss.org/browse/ISPN-4088 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 64QueryBlockers > Fix For: 7.1.0.CR1 > > > The method exists in both new DSL and the classic query api. > It should be clarified whether this method and the related pagination methods should use int or long for specifying offsets within the data, also should decide if the total number of results / results per page is a long or an int - and update all involved method signatures to have a unitary treatment of this issue. > It appears that recent Lucene versions can offer the number of results as long, while older ones offer it as int (should be verified). > This issue was raised in a github conversation here: https://github.com/infinispan/infinispan/pull/2410 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4136) Declarative config for REST rawValues

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4136?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4136: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3204 > Declarative config for REST rawValues > ------------------------------------- > > Key: ISPN-4136 > URL: https://issues.jboss.org/browse/ISPN-4136 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Tristan Tarrant > Fix For: 7.1.0.CR1 > > > Once ISPN-3514 is in we can add support for the REST rawValues boolean in the new 7.0 parser -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4136) Declarative config for REST rawValues

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4136?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4136: ------------------------------------- Assignee: Tristan Tarrant > Declarative config for REST rawValues > ------------------------------------- > > Key: ISPN-4136 > URL: https://issues.jboss.org/browse/ISPN-4136 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.1.0.CR1 > > > Once ISPN-3514 is in we can add support for the REST rawValues boolean in the new 7.0 parser -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5143) Deploying a cache converter on its own (wo/ filter) fails to deploy

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5143: -------------------------------------- Summary: Deploying a cache converter on its own (wo/ filter) fails to deploy Key: ISPN-5143 URL: https://issues.jboss.org/browse/ISPN-5143 Project: Infinispan Issue Type: Bug Components: Listeners, Remote Protocols, Server Affects Versions: 7.0.3.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 7.1.0.CR1, 7.1.0.Final, 7.0.4.Final A converter jar deployment, without any other filters, throws the following: {code} 14:37:02,523 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "converter.jar" (runtime-name: "converter.jar") 14:37:02,536 WARN [org.jboss.modules] (MSC service thread 1-8) Failed to define class org.infinispan.server.test.client.hotrod.StaticCacheEventConverterFactory in Module "deployment.converter.jar:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/infinispan/server/test/client/hotrod/StaticCacheEventConverterFactory (Module "deployment.converter.jar:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] at org.infinispan.server.endpoint.deployments.AbstractServerExtensionProcessor.addServices(AbstractServerExtensionProcessor.java:34) at org.infinispan.server.endpoint.deployments.AbstractServerExtensionProcessor.deploy(AbstractServerExtensionProcessor.java:25) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] Caused by: java.lang.NoClassDefFoundError: org/infinispan/notifications/cachelistener/filter/CacheEventConverterFactory at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_60] at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_60] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.3.Final] ... 16 more Caused by: java.lang.ClassNotFoundException: org.infinispan.notifications.cachelistener.filter.CacheEventConverterFactory from [Module "deployment.converter.jar:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] ... 20 more {code} If converter is deployed along with a filter, it works fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3549) Migrate cloud cache store to the 7.0 cachestore API

by Damiano Albani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3549?page=com.atlassian.jira.plugin.... ] Damiano Albani commented on ISPN-3549: -------------------------------------- You might be interested in looking at the code that I wrote: https://github.com/snotling/infinispan-cachestore-cloud I had absolutely no experience with Infinispan so I took my inspiration from the REST and JDBC cache store implementations. > Migrate cloud cache store to the 7.0 cachestore API > ---------------------------------------------------- > > Key: ISPN-3549 > URL: https://issues.jboss.org/browse/ISPN-3549 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Vojtech Juranek > -- 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