August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6767) Upgrade to Hibernate ORM 5.1.1.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6767?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6767: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4518, https://github.com/infinispan/infinispan/pull/4519, https://github.com/infinispan/infinispan/pull/4522 (was: https://github.com/infinispan/infinispan/pull/4518, https://github.com/infinispan/infinispan/pull/4522) > Upgrade to Hibernate ORM 5.1.1.Final > ------------------------------------ > > Key: ISPN-6767 > URL: https://issues.jboss.org/browse/ISPN-6767 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6767) Upgrade to Hibernate ORM 5.1.1.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6767?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6767: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4518, https://github.com/infinispan/infinispan/pull/4522 (was: https://github.com/infinispan/infinispan/pull/4518) > Upgrade to Hibernate ORM 5.1.1.Final > ------------------------------------ > > Key: ISPN-6767 > URL: https://issues.jboss.org/browse/ISPN-6767 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6937) infinispan-core should not depend on Kubernetes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6937?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6937: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > infinispan-core should not depend on Kubernetes > ----------------------------------------------- > > Key: ISPN-6937 > URL: https://issues.jboss.org/browse/ISPN-6937 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha4 > Reporter: Gustavo Fernandes > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6956) AffinityPartitioner enabled as default partitioner

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6956?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6956: ---------------------------------- Status: Open (was: New) > AffinityPartitioner enabled as default partitioner > -------------------------------------------------- > > Key: ISPN-6956 > URL: https://issues.jboss.org/browse/ISPN-6956 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > > Having the {{org.infinispan.distribution.ch.impl.AffinityPartitioner}} as default enabled {{KeyPartitioner}} will allow people to use the functionality offered by {{org.infinispan.distribution.ch.AffinityTaggedKey}} out of the box, without needing to enable it explicitly in configuration. > {{AffinityTaggedKey}} is used by Query but not only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6956) AffinityPartitioner enabled as default partitioner

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-6956?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-6956: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4521 > AffinityPartitioner enabled as default partitioner > -------------------------------------------------- > > Key: ISPN-6956 > URL: https://issues.jboss.org/browse/ISPN-6956 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > > Having the {{org.infinispan.distribution.ch.impl.AffinityPartitioner}} as default enabled {{KeyPartitioner}} will allow people to use the functionality offered by {{org.infinispan.distribution.ch.AffinityTaggedKey}} out of the box, without needing to enable it explicitly in configuration. > {{AffinityTaggedKey}} is used by Query but not only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6956) AffinityPartitioner enabled as default partitioner

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-6956: ------------------------------------- Summary: AffinityPartitioner enabled as default partitioner Key: ISPN-6956 URL: https://issues.jboss.org/browse/ISPN-6956 Project: Infinispan Issue Type: Enhancement Components: Core Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 9.0.0.Beta1 Having the {{org.infinispan.distribution.ch.impl.AffinityPartitioner}} as default enabled {{KeyPartitioner}} will allow people to use the functionality offered by {{org.infinispan.distribution.ch.AffinityTaggedKey}} out of the box, without needing to enable it explicitly in configuration. {{AffinityTaggedKey}} is used by Query but not only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5833) ModuleCommandExtensions should not expose deprecated type ExtendedModuleCommandFactory

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5833?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5833: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks [~sannegrinovero]! > ModuleCommandExtensions should not expose deprecated type ExtendedModuleCommandFactory > --------------------------------------------------------------------------------------- > > Key: ISPN-5833 > URL: https://issues.jboss.org/browse/ISPN-5833 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Final > > > The {{ModuleCommandExtensions}} SPI is exposing a type which is deprecated, it's parent type should be used instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5467: ------------------------------------ [~belaban] it's probably worth a wiki page, but I'm going to add a brief description here :) I've just issued a new [PR|https://github.com/infinispan/infinispan/pull/4520], so that's what I'm going to describe. * Interceptors extending {{CommandInterceptor}} still work, and can use only {{invokeNext(ctx, command)}} to invoke the next interceptor synchronously. * The new base class is {{BaseAsyncInterceptor}}, which defines a single {{visitCommand(InvocationContext, VisitableCommand)}} entry point. * {{DDAsyncInterceptor}} extends {{BaseAsyncInterceptor}} to add the familiar {{visitXCommand(\[Tx\]InvocationContext, XCommand)}} entry points. * The return type of the {{visitXCommand}} methods is {{BasicInvocationStage}}, only allow you to extract a value or convert to a {{CompletableFuture}}. * {{BaseAsyncInterceptor}} defines some methods that return a {{BasicInvocationStage}}, or a more feature-full {{InterceptorStage}} instance: ** {{invokeNext(ctx, command)}} works just like {{CommandInterceptor.invokeNext}}, except the invocation may be asynchronous. ** {{returnWith(value)}} returns a value, because we can't just return a value directly. ** {{goAsync(CompletableFuture<BasicInvocationStage>}} continues the invocation asynchronously. ** {{invokeNextAsync(ctx, command, future)}} is a shortcut for {{goAsync(f.thenApply(o -> invokeNext(ctx, command)))}. ** {{returnWithAsync(value)}} is a shortcut for {{goAsync(f.thenApply(o -> returnWith(ctx, command)))}. * {{InvocationStage}} extends {{BasicInvocationStage}} with a few more {{CompletionStage}}-like features. The main differences from {{CompletionStage}} are: ** All callbacks receive two extra parameters: the context and the command. In many interceptors, this allows us to store the callback in a field instead of creating a new instance on each invocation. ** Callbacks can throw {{Throwable}}, and received exceptions are not wrapped in `CompletionException`. I'm on the edge about this, but I'm sure a switch to `CompletionException` wrapping should be have a separate issue anyway. ** Not all {{CompletionStage}} methods are implemented, e.g. we don't support combining two invocation stages with {{thenCombine}}. ** We also have one extra method, {{compose((BasicInvocationStage, InvocationStage, VisitableCommand, Object, Throwable) -> BasicInvocationStage. It works like {{CompletionStage.thenCompose}}, but the callback gets called even if the invocation stage failed. > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5467: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3819, https://github.com/infinispan/infinispan/pull/4520 (was: https://github.com/infinispan/infinispan/pull/3819) > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6032) InfinispanRemoteCacheManagerFactoryBeanTest.shouldProduceACacheConfiguredUsingPropertiesLoadedFromALocationDeclaredThroughSetConfigurationPropertiesFileLocation/shouldProduceACacheConfiguredUsingTheSuppliedConfigurationProperties fail

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6032?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-6032: ----------------------------------------- Assignee: Sebastian Łaskawiec > InfinispanRemoteCacheManagerFactoryBeanTest.shouldProduceACacheConfiguredUsingPropertiesLoadedFromALocationDeclaredThroughSetConfigurationPropertiesFileLocation/shouldProduceACacheConfiguredUsingTheSuppliedConfigurationProperties fail > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6032 > URL: https://issues.jboss.org/browse/ISPN-6032 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Roman Macor > Assignee: Sebastian Łaskawiec > > Error Message > The configuration properties used by the RemoteCacheManager returned by getObject() should be equal to those passed into InfinispanRemoteCacheMangerFactoryBean via setConfigurationPropertiesFileLocation(propsFileLocation). However, those two are not equal. Key infinispan.client.hotrod.ping_on_startup missing from {infinispan.client.hotrod.marshaller=org.infinispan.commons.marshall.jboss.GenericJBossMarshaller, maxIdle=97, maxTotal=98, minEvictableIdleTimeMillis=1800000, infinispan.client.hotrod.connect_timeout=60000, testOnBorrow=false, maxWait=-1, infinispan.client.hotrod.server_list=127.0.0.1:19733, infinispan.client.hotrod.tcp_no_delay=true, testWhileIdle=true, infinispan.client.hotrod.default_executor_factory.queue_size=10000, maxActive=99, infinispan.client.hotrod.async_executor_factory=org.infinispan.client.hotrod.impl.async.DefaultAsyncExecutorFactory, infinispan.client.hotrod.default_executor_factory.pool_size=1, infinispan.client.hotrod.key_size_estimate=64, infinispan.client.hotrod.hash_function_impl.3=org.infinispan.client.hotrod.impl.consistenthash.SegmentConsistentHash, infinispan.client.hotrod.hash_function_impl.2=org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV2, lifo=true, infinispan.client.hotrod.hash_function_impl.1=org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV1, infinispan.client.hotrod.max_retries=10, timeBetweenEvictionRunsMillis=120000, infinispan.client.hotrod.socket_timeout=60000, exhaustedAction=1, infinispan.client.hotrod.protocol_version=2.3, infinispan.client.hotrod.tcp_keep_alive=false, infinispan.client.hotrod.value_size_estimate=512, testOnReturn=false, infinispan.client.hotrod.force_return_values=false, infinispan.client.hotrod.transport_factory=org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory, numTestsPerEvictionRun=3, infinispan.client.hotrod.request_balancing_strategy=org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy, minIdle=1} > Stacktrace > java.lang.AssertionError: The configuration properties used by the RemoteCacheManager returned by getObject() should be equal to those passed into InfinispanRemoteCacheMangerFactoryBean via setConfigurationPropertiesFileLocation(propsFileLocation). However, those two are not equal. Key infinispan.client.hotrod.ping_on_startup missing from {infinispan.client.hotrod.marshaller=org.infinispan.commons.marshall.jboss.GenericJBossMarshaller, maxIdle=97, maxTotal=98, minEvictableIdleTimeMillis=1800000, infinispan.client.hotrod.connect_timeout=60000, testOnBorrow=false, maxWait=-1, infinispan.client.hotrod.server_list=127.0.0.1:19733, infinispan.client.hotrod.tcp_no_delay=true, testWhileIdle=true, infinispan.client.hotrod.default_executor_factory.queue_size=10000, maxActive=99, infinispan.client.hotrod.async_executor_factory=org.infinispan.client.hotrod.impl.async.DefaultAsyncExecutorFactory, infinispan.client.hotrod.default_executor_factory.pool_size=1, infinispan.client.hotrod.key_size_estimate=64, infinispan.client.hotrod.hash_function_impl.3=org.infinispan.client.hotrod.impl.consistenthash.SegmentConsistentHash, infinispan.client.hotrod.hash_function_impl.2=org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV2, lifo=true, infinispan.client.hotrod.hash_function_impl.1=org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV1, infinispan.client.hotrod.max_retries=10, timeBetweenEvictionRunsMillis=120000, infinispan.client.hotrod.socket_timeout=60000, exhaustedAction=1, infinispan.client.hotrod.protocol_version=2.3, infinispan.client.hotrod.tcp_keep_alive=false, infinispan.client.hotrod.value_size_estimate=512, testOnReturn=false, infinispan.client.hotrod.force_return_values=false, infinispan.client.hotrod.transport_factory=org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory, numTestsPerEvictionRun=3, infinispan.client.hotrod.request_balancing_strategy=org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy, minIdle=1} > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) > at org.infinispan.spring.AssertionUtils.assertPropertiesSubset(AssertionUtils.java:11) > at org.infinispan.spring.support.remote.InfinispanRemoteCacheManagerFactoryBeanTest.shouldProduceACacheConfiguredUsingPropertiesLoadedFromALocationDeclaredThroughSetConfigurationPropertiesFileLocation(InfinispanRemoteCacheManagerFactoryBeanTest.java:205) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 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 August 2016