September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3530) The HotRod client should support a separate CH for each cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3530?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3530: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > The HotRod client should support a separate CH for each cache > ------------------------------------------------------------- > > Key: ISPN-3530 > URL: https://issues.jboss.org/browse/ISPN-3530 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 6.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: hotrod, hotrod-java-client > > With asymmetric clusters, each cache can have its own consistent hash, so the primary owner of a key in one cache is not necessarily the owner in all the caches. Even with a symmetric cluster, the same client may be used to access both distributed and replicated caches, and those would certainly have a different CH. > In order to send the operations to the correct owner, the HotRod client should use a different CH for each cache. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3539) Allow adding multiple custom interceptors without calling customInterceptors() every time

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-3539: --------------------------------- Summary: Allow adding multiple custom interceptors without calling customInterceptors() every time Key: ISPN-3539 URL: https://issues.jboss.org/browse/ISPN-3539 Project: Infinispan Issue Type: Enhancement Reporter: Jiří Holuša Assignee: Mircea Markus Priority: Minor When adding multiple custom interceptors programmatically via ConfigurationBuilder, you have to call customInterceptors() every time you want to add a new one. The code than looks like this: {code:borderStyle=solid} Configuration c2 = new ConfigurationBuilder() .customInterceptors() .addInterceptor() .position(InterceptorConfiguration.Position.FIRST).interceptor(new FirstInterceptor(1)) .customInterceptors() .addInterceptor() .after(FirstInterceptor.class).interceptor(new SecondInterceptor(2)) .build(); {code} I think this is very ugly and it would be nice and even semantically more meaningful to do it like: {code:borderStyle=solid} Configuration c2 = new ConfigurationBuilder() .customInterceptors() .addInterceptor() .position(InterceptorConfiguration.Position.FIRST).interceptor(new FirstInterceptor(1)) .addInterceptor() .after(FirstInterceptor.class).interceptor(new SecondInterceptor(2)) .build(); {code} e.g. calling customInterceptors() only once. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3538) Align recovery() enabling in Configuration

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-3538: --------------------------------- Summary: Align recovery() enabling in Configuration Key: ISPN-3538 URL: https://issues.jboss.org/browse/ISPN-3538 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 6.0.0.Beta1 Reporter: Jiří Holuša Assignee: Mircea Markus Priority: Minor When configuring recovery via ConfigurationBuilder, calling .transaction().recovery() will by default enable recovery, so no need to call enable(). But when calling e.g. globalJmxStatistics() in GlobalConfigurationBuilder, you have to explicitly call enable(). Another example is when configuring L1 cache, e.g. l1().lifespan(60000L), you also have to explicitly call enable(). I think it would be nice to have it consistent. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3537) Custom interceptor with Position.LAST set programmatically doesn't work

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-3537: --------------------------------- Summary: Custom interceptor with Position.LAST set programmatically doesn't work Key: ISPN-3537 URL: https://issues.jboss.org/browse/ISPN-3537 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 6.0.0.Beta1 Reporter: Jiří Holuša Assignee: Mircea Markus When configuring cache programmatically, adding a custom interceptor with position set to Position.LAST cause not calling this interceptor. Code sample: {code:borderStyle=solid} EmbeddedCacheManager manager = new DefaultCacheManager(); Configuration c2 = new ConfigurationBuilder() .customInterceptors() .addInterceptor() .position(InterceptorConfiguration.Position.LAST).interceptor(new MyInterceptor()) .build(); manager.defineConfiguration("interceptors", c2); Cache<String, String> cache = manager.getCache("interceptors"); cache.put("hello", "world"); {code} MyInterceptor is very simple, reacting to all events. When changing to Position.FIRST, everything works fine. Also tried two/three interceptors, various combinations, but always with same result - when position set to Position.LAST, interceptors is not called. Note that no problem when setting by index(). -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2050) Query is attempting to run a KeyTransformer on types which are not meant to be indexed

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2050?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2050: --------------------------------------- No, it was reported by users. > Query is attempting to run a KeyTransformer on types which are not meant to be indexed > -------------------------------------------------------------------------------------- > > Key: ISPN-2050 > URL: https://issues.jboss.org/browse/ISPN-2050 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.1.3.FINAL > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: stable_embedded_query > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3349) Remove JCache dependency from CDI module

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3349?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3349: ----------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.CR1) > Remove JCache dependency from CDI module > ---------------------------------------- > > Key: ISPN-3349 > URL: https://issues.jboss.org/browse/ISPN-3349 > Project: Infinispan > Issue Type: Enhancement > Components: CDI integration, JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Beta2 > > > Move InjectedCacheResolver to jcache/ module, avoiding CDI module's dependency on JCache module. On top of that, existing CDI+JCache integration tests should be moved to a dedicated test project under https://github.com/infinispan/infinispan/tree/master/integrationtests -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3349) Remove JCache dependency from CDI module

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3349?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3349: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2092 > Remove JCache dependency from CDI module > ---------------------------------------- > > Key: ISPN-3349 > URL: https://issues.jboss.org/browse/ISPN-3349 > Project: Infinispan > Issue Type: Enhancement > Components: CDI integration, JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.CR1 > > > Move InjectedCacheResolver to jcache/ module, avoiding CDI module's dependency on JCache module. On top of that, existing CDI+JCache integration tests should be moved to a dedicated test project under https://github.com/infinispan/infinispan/tree/master/integrationtests -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3345) CachePutInterceptorTest does not always close cache managers

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3345?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3345: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2091 > CachePutInterceptorTest does not always close cache managers > ------------------------------------------------------------ > > Key: ISPN-3345 > URL: https://issues.jboss.org/browse/ISPN-3345 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 6.0.0.Final > > > Sometimes CDI's CachePutInterceptorTest fails to close all cache managers: > {code} > [16:39:06][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test putWithCacheKeyGenerator(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:06][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 29, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePut(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 30, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutBeforeInvocation(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 31, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutCacheKeyParam(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 32, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutWithCacheName(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 33, failed: 0, skipped: 0. > [16:40:07][org.infinispan:infinispan-cdi] > [16:40:07][org.infinispan:infinispan-cdi] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!! (testng-CachePutInterceptorTest) Exiting because CachePutInterceptorTest has NOT shut down all the cache managers it has started !!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!! (testng-CachePutInterceptorTest) The still-running cacheManager was created here: org.infinispan.cdi.AdvancedCacheProducer.getAdvancedCache(AdvancedCacheProducer.java:67) !!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] {code} -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3345) CachePutInterceptorTest does not always close cache managers

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3345?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3345: ----------------------------------- Fix Version/s: 6.0.0.Beta2 > CachePutInterceptorTest does not always close cache managers > ------------------------------------------------------------ > > Key: ISPN-3345 > URL: https://issues.jboss.org/browse/ISPN-3345 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 6.0.0.Beta2, 6.0.0.Final > > > Sometimes CDI's CachePutInterceptorTest fails to close all cache managers: > {code} > [16:39:06][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test putWithCacheKeyGenerator(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:06][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 29, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePut(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 30, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutBeforeInvocation(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 31, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutCacheKeyParam(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 32, failed: 0, skipped: 0. > [16:39:07][org.infinispan:infinispan-cdi] [testng-CachePutInterceptorTest] Test testCachePutWithCacheName(org.infinispan.cdi.test.interceptor.CachePutInterceptorTest) succeeded. > [16:39:07][org.infinispan:infinispan-cdi] Test suite progress: tests succeeded: 33, failed: 0, skipped: 0. > [16:40:07][org.infinispan:infinispan-cdi] > [16:40:07][org.infinispan:infinispan-cdi] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!! (testng-CachePutInterceptorTest) Exiting because CachePutInterceptorTest has NOT shut down all the cache managers it has started !!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!! (testng-CachePutInterceptorTest) The still-running cacheManager was created here: org.infinispan.cdi.AdvancedCacheProducer.getAdvancedCache(AdvancedCacheProducer.java:67) !!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [16:40:07][org.infinispan:infinispan-cdi] {code} -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3330) Hotrod clients getWithMetadata doesn't work when locking isolation != NONE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3330?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3330: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 987524|https://bugzilla.redhat.com/show_bug.cgi?id=987524] from ASSIGNED to ON_QA > Hotrod clients getWithMetadata doesn't work when locking isolation != NONE > -------------------------------------------------------------------------- > > Key: ISPN-3330 > URL: https://issues.jboss.org/browse/ISPN-3330 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 6.0.0.Alpha4 > Reporter: Jakub Markos > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 6.0.0.Beta1, 6.0.0.Final > > > I have a cluster of 2 infinispan servers with this configuration: > {code:xml}<subsystem xmlns="urn:infinispan:server:core:5.3"> > <cache-container name="default" default-cache="default" listener-executor="infinispan-listener"> > <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/> > <distributed-cache name="default" start="EAGER" mode="SYNC" segments="1" owners="2" batching="false" l1-lifespan="0" remote-timeout="60000"> > <locking isolation="REPEATABLE_READ"/> > </distributed-cache> > </cache-container> > </subsystem>{code} > Running this code: > {code}remoteCache.put("k1", "v1", 10000000, TimeUnit.MICROSECONDS); // setting only lifespan > MetadataValue<String> k1 = remoteCache.getWithMetadata("k1"); > assertTrue(k1.getValue().equals("v1")); > // microseconds converted to seconds > assertTrue(k1.getLifespan() == 10); > assertTrue(k1.getMaxIdle() == -1);{code} > fails with: > {code}org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[5] returned server error (status=0x85): java.lang.ClassCastException: org.infinispan.container.entries.RepeatableReadEntry can > not be cast to org.infinispan.container.entries.InternalCacheEntry > at org.infinispan.client.hotrod.impl.protocol.Codec10.checkForErrorsInResponseStatus(Codec10.java:143) > at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:99) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.sendKeyOperation(AbstractKeyOperation.java:52) > at org.infinispan.client.hotrod.impl.operations.GetWithMetadataOperation.executeOperation(GetWithMetadataOperation.java:35) > at org.infinispan.client.hotrod.impl.operations.GetWithMetadataOperation.executeOperation(GetWithMetadataOperation.java:23) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:46) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.getWithMetadata(RemoteCacheImpl.java:145){code} > Works with isolation="READ_COMMITED"/"NONE" or with no <locking> at all. -- 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

12 years, 6 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 September 2013