March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5195) CacheConfigurationException when two methods using default cache configuration are called in same request

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-5195?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec resolved ISPN-5195. --------------------------------------- Fix Version/s: 7.2.0.CR1 Resolution: Done > CacheConfigurationException when two methods using default cache configuration are called in same request > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-5195 > URL: https://issues.jboss.org/browse/ISPN-5195 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Marcio Dantas > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: cacheresult, cdi, infinispan, injectedcacheresolver > Fix For: 7.2.0.CR1 > > Attachments: cdi-quickstart-7.1.1.Final.zip, infinispan-cdi.tar.gz > > > When two methods annotated with @CacheResult (without cacheName specified) are called in the same request, then the following error occurs: > {panel} > org.infinispan.commons.CacheConfigurationException: Detected interceptor of type [org.infinispan.jcache.interceptor.ExpirationTrackingInterceptor] being added to the interceptor chain 1743453620 more than once! > at org.infinispan.interceptors.InterceptorChain.assertNotAdded(InterceptorChain.java:76) > at org.infinispan.interceptors.InterceptorChain.addInterceptorBefore(InterceptorChain.java:248) > at org.infinispan.CacheImpl.addInterceptorBefore(CacheImpl.java:717) > at org.infinispan.jcache.JCache.addExpirationTrackingInterceptor(JCache.java:158) > at org.infinispan.jcache.JCache.<init>(JCache.java:111) > at org.infinispan.jcache.JCacheManager.configureCache(JCacheManager.java:238) > at org.infinispan.jcache.annotation.InjectedCacheResolver.getCacheFromDefaultCacheManager(InjectedCacheResolver.java:105) > at org.infinispan.jcache.annotation.InjectedCacheResolver.resolveCache(InjectedCacheResolver.java:97) > at org.infinispan.jcache.annotation.InjectedCacheResolver$Proxy$_$$_WeldClientProxy.resolveCache(InjectedCacheResolver$Proxy$_$$_WeldClientProxy.java) > at org.infinispan.jcache.annotation.AbstractCacheResultInterceptor.cacheResult(AbstractCacheResultInterceptor.java:56) > at org.infinispan.jcache.annotation.InjectedCacheResultInterceptor.cacheResult(InjectedCacheResultInterceptor.java:33) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) > at org.jboss.weld.interceptor.proxy.SimpleInterceptionChain.invokeNextInterceptor(SimpleInterceptionChain.java:69) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:112) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:88) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:55) > at org.infinispan.quickstart.cdi.GreetingService$Proxy$_$$_WeldSubclass.greetDefaultCacheConfigTwo(GreetingService$Proxy$_$$_WeldSubclass.java) > at org.infinispan.quickstart.cdi.GreetingController.greet(GreetingController.java:58) > at org.infinispan.quickstart.cdi.GreetingController$Proxy$_$$_WeldClientProxy.greet(GreetingController$Proxy$_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.el.parser.AstValue.invoke(AstValue.java:258) > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40) > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) > at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:87) > ... 21 more > {panel} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2145) No descriptions for invalid jgroups configuration files

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2145?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2145: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > No descriptions for invalid jgroups configuration files > ------------------------------------------------------- > > Key: ISPN-2145 > URL: https://issues.jboss.org/browse/ISPN-2145 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 5.1.2.FINAL, 7.0.0.CR1 > Environment: Any > Reporter: Dmitry Udalov > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1 > > > Can't find error's description for invalid jgroups configuration files. Shuffling elements of the file (why not!) makes it invalid, but log-files only report the existence of the error and you have to debug it to figure out the problem. It would be easier if the class JGroupsTransport also reports the exception, not just a generic message in blocks like > } catch (Exception e) { > log.errorCreatingChannelFromConfigFile(cfg); > throw new CacheException(e); > } > As a result log-file contains a lot of generic messages without explaining the problem, which in my case was quite helpful: > java.lang.Exception: events [GET_DIGEST SET_DIGEST FIND_INITIAL_MBRS FIND_ALL_VIEWS ] are required by GMS, but not provided by any of the protocols below it -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2939) Remove option for async Marshalling

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2939?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2939: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Remove option for async Marshalling > ----------------------------------- > > Key: ISPN-2939 > URL: https://issues.jboss.org/browse/ISPN-2939 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Pedro Ruivo > Priority: Minor > Fix For: 7.2.0.CR1 > > > Seems to introduce inconsistencies - and generally hard to figure out how to configure properly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3159) Implementing SERIALIZABLE isolation level based on GMU

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3159?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3159: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Implementing SERIALIZABLE isolation level based on GMU > ------------------------------------------------------ > > Key: ISPN-3159 > URL: https://issues.jboss.org/browse/ISPN-3159 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.2.0.CR1 > > > Implementation based in GMU, a Cloud-TM project research (www.cloudtm.eu). > GMU is a muti-version scheme that provides Update Serializability. It allows the read-only transaction to proceed without blocking, but they can observe an old value (but always a consistent value). > This scheme relies in Vector Clock to manage the snapshots to read and the transaction dependencies in each node in the cluster. > Also, it is a genuine scheme, i.e., only the nodes involved in the transaction (that contains data read or write) are involved in the transaction commit. > A paper describing GMU can be found here: http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=62... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3729) Minimize the number of moved segments for SyncConsistentHashFactory

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3729?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3729: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Minimize the number of moved segments for SyncConsistentHashFactory > ------------------------------------------------------------------- > > Key: ISPN-3729 > URL: https://issues.jboss.org/browse/ISPN-3729 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.2.0.CR1 > > > SyncConsistentHash uses an algorithm that's similar to consistent hashing, but when there is a collision (two nodes map to the same segment), the second node is moved to the next segment. Since the nodes are ordered by their UUID, that means it's possible for a joiner to change the mapping of existing nodes. > In order to make the load distribution more even, SyncConsistentHash also uses "virtual nodes": each node actually maps to multiple segments. This makes the number of collisions much higher (and implicitly, the number of extra moved segments). > Reading the original [consistent hashing paper|http://thor.cs.ucsb.edu/~ravenben/papers/coreos/kll%2B97.pdf], it looks like the collision handling should be done differently: a joiner should replace an existing node when it's "closer" to the segment boundary, but the existing node should never "lose" segments to another existing node (the property of monotonicity mentioned in the paper). We should investigate whether changing this would allow us to achieve better load balancing by using a much higher number of "virtual nodes" (without moving extra segments). If successful, we could even use SyncConsistentHashFactory as the default hash algorithm. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3344) Create a release script for ProtoStream library

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3344?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3344: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Create a release script for ProtoStream library > ----------------------------------------------- > > Key: ISPN-3344 > URL: https://issues.jboss.org/browse/ISPN-3344 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 6.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1 > > > Need to add license information and a short README to the project. Also update the 'Cutting Infinispan Releases' document with relevant details for Protostream. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3891: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Fix For: 7.2.0.CR1 > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3835: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 7.2.0.CR1 > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3906: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1 > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3905) Murmurhash3 implementation is slow on String keys

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3905?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3905: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Murmurhash3 implementation is slow on String keys > ------------------------------------------------- > > Key: ISPN-3905 > URL: https://issues.jboss.org/browse/ISPN-3905 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > Fix For: 7.2.0.CR1 > > > String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too. > I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015