February 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5204) Don't include old schema files in the documentation and jars/distribution

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5204?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-5204: ---------------------------- Summary: Don't include old schema files in the documentation and jars/distribution (was: Include in configdocs only the schema from the current version) Description: Include in configdocs/, jars and distribution only the scheme matching *-<version.major>.<version.minor>.xsd (was: Include in configdocs/ only the scheme matching *-<version.major>.<version.minor>.xsd) Component/s: Build process > Don't include old schema files in the documentation and jars/distribution > ------------------------------------------------------------------------- > > Key: ISPN-5204 > URL: https://issues.jboss.org/browse/ISPN-5204 > Project: Infinispan > Issue Type: Enhancement > Components: Build process, Documentation-Core > Affects Versions: 7.1.0.Final > Reporter: Ion Savin > Assignee: Ion Savin > > Include in configdocs/, jars and distribution only the scheme matching *-<version.major>.<version.minor>.xsd -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5206) Don't include schemas from other versions in the jars and distribution

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5206?page=com.atlassian.jira.plugin.... ] Ion Savin deleted ISPN-5206: ---------------------------- > Don't include schemas from other versions in the jars and distribution > ---------------------------------------------------------------------- > > Key: ISPN-5206 > URL: https://issues.jboss.org/browse/ISPN-5206 > Project: Infinispan > Issue Type: Enhancement > Reporter: Ion Savin > Assignee: Ion Savin > > If schemas from the previous version are not removed from VC they will be included in the jars and distribution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5206) Don't include schemas from other versions in the jars and distribution

by Ion Savin (JIRA)

Ion Savin created ISPN-5206: ------------------------------- Summary: Don't include schemas from other versions in the jars and distribution Key: ISPN-5206 URL: https://issues.jboss.org/browse/ISPN-5206 Project: Infinispan Issue Type: Enhancement Components: Build process Affects Versions: 7.1.0.Final Reporter: Ion Savin Assignee: Ion Savin If schemas from the previous version are not removed from VC they will be included in the jars and distribution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5205) CacheResult Interceptor creates wrong CacheManager

by Bruno Palaoro (JIRA)

[ https://issues.jboss.org/browse/ISPN-5205?page=com.atlassian.jira.plugin.... ] Bruno Palaoro updated ISPN-5205: -------------------------------- Description: If I use the CacheResult interceptor, it won't create the correct CacheManager. It seems that it always create using the default options, it doesn't matter the configurations I've used. In the attached example, the items are never added to the cache I inject in the GreetingCacheManager, seems like two different caches, one inside @CacheResult and when I inject its another. I've tried using the InjectCacheResult, and it solve this issue, but then another one rises, as described in issue 5195 (https://issues.jboss.org/browse/ISPN-5195) was:If I use the CacheResult interceptor, it won't create the correct CacheManager. It seems that it always create using the default options, it doesn't matter the configurations I've used. > CacheResult Interceptor creates wrong CacheManager > -------------------------------------------------- > > Key: ISPN-5205 > URL: https://issues.jboss.org/browse/ISPN-5205 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.2.Final > Reporter: Bruno Palaoro > Priority: Critical > Attachments: infinispan-cdi.zip > > > If I use the CacheResult interceptor, it won't create the correct CacheManager. It seems that it always create using the default options, it doesn't matter the configurations I've used. > In the attached example, the items are never added to the cache I inject in the GreetingCacheManager, seems like two different caches, one inside @CacheResult and when I inject its another. > I've tried using the InjectCacheResult, and it solve this issue, but then another one rises, as described in issue 5195 (https://issues.jboss.org/browse/ISPN-5195) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5205) CacheResult Interceptor creates wrong CacheManager

by Bruno Palaoro (JIRA)

[ https://issues.jboss.org/browse/ISPN-5205?page=com.atlassian.jira.plugin.... ] Bruno Palaoro updated ISPN-5205: -------------------------------- Attachment: infinispan-cdi.zip > CacheResult Interceptor creates wrong CacheManager > -------------------------------------------------- > > Key: ISPN-5205 > URL: https://issues.jboss.org/browse/ISPN-5205 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 6.0.2.Final > Reporter: Bruno Palaoro > Priority: Critical > Attachments: infinispan-cdi.zip > > > If I use the CacheResult interceptor, it won't create the correct CacheManager. It seems that it always create using the default options, it doesn't matter the configurations I've used. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5205) CacheResult Interceptor creates wrong CacheManager

by Bruno Palaoro (JIRA)

Bruno Palaoro created ISPN-5205: ----------------------------------- Summary: CacheResult Interceptor creates wrong CacheManager Key: ISPN-5205 URL: https://issues.jboss.org/browse/ISPN-5205 Project: Infinispan Issue Type: Bug Components: CDI Integration Affects Versions: 6.0.2.Final Reporter: Bruno Palaoro Priority: Critical If I use the CacheResult interceptor, it won't create the correct CacheManager. It seems that it always create using the default options, it doesn't matter the configurations I've used. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5203) Protostream annotation attributes that do not have a default value should be required

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5203?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5203: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. > Protostream annotation attributes that do not have a default value should be required > ------------------------------------------------------------------------------------- > > Key: ISPN-5203 > URL: https://issues.jboss.org/browse/ISPN-5203 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2981) Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2981?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2981: --------------------------------------- The description of this issue could be caused by many things. I'm pretty sure the original bug was resolved in 7.0, and the Hibernate Search version you use for this is irrelevant. But there are other possible problems which could lead to seeing this same error message, for example if Infinispan fails to store something then it's obviously going to complain that something which was supposed to be stored won't be found. You might have such storage failures caused by a previous exception, and not least by general load/efficiency/performance issues as the ones you described on the forums post. To improve performance, one of our blind guesses is to upgrade to 7.1 and latest Hibernate Search.. but ultimately you're dealing with a severe performance problem, possibly a network configuration issue, and as I suggested on the forums you need to use some diagnostic tools to identify this. The original issue here was resolved, so let's not discuss here. If you need more help with diagnostics, or general suggestions the forums is the right place. If you have a test which can reproduce an issue like this one, please create a new JIRA and attach it I'll be very glad to look at it. Regarding API changes: we work hard to keep the API stable but this promise doesn't apply to Beta releases. > Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-2981 > URL: https://issues.jboss.org/browse/ISPN-2981 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.4.Final > Environment: Hibernate Search 4.1.1, Hibernate Core 4.1.4, Lucene 3.5.0, Spring Framework 3.1.1 > Reporter: Christopher Wong > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta2, 7.0.0.Final > > Attachments: infinispan.cfg.xml, luceneindexerrors.txt > > > I have been trying to use Infinispan as a Lucene directory provider under Hibernate Search. A single node writes to the index via JMS. A configuration that uses Infinispan in distributed mode seems to work under development, but under load results in an exception that looks like the following. > Caused by: java.io.IOException: No sub-file with id .fnm found (fileName=_3.cfs files: [.fdt, .fdx]) > at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:156) > at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:145) > at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:74) > at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:73) > at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:115) > at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:93) > at org.apache.lucene.index.DirectoryReader.<init>(DirectoryReader.java:235) > at org.apache.lucene.index.ReadOnlyDirectoryReader.<init>(ReadOnlyDirectoryReader.java:34) > at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:506) > at org.apache.lucene.index.DirectoryReader.access$000(DirectoryReader.java:45) > at org.apache.lucene.index.DirectoryReader$2.doBody(DirectoryReader.java:498) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754) > at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:493) > at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:450) > at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:391) > at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:497) > at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:681) > at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:227) > ... 117 more -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5204) Include in configdocs only the schema from the current version

by Ion Savin (JIRA)

Ion Savin created ISPN-5204: ------------------------------- Summary: Include in configdocs only the schema from the current version Key: ISPN-5204 URL: https://issues.jboss.org/browse/ISPN-5204 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Affects Versions: 7.1.0.Final Reporter: Ion Savin Assignee: Ion Savin Include in configdocs/ only the scheme matching *-<version.major>.<version.minor>.xsd -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

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

by Marcio Dantas (JIRA)

[ https://issues.jboss.org/browse/ISPN-5195?page=com.atlassian.jira.plugin.... ] Marcio Dantas updated ISPN-5195: -------------------------------- Priority: Critical (was: Major) > 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 > Reporter: Marcio Dantas > Priority: Critical > Labels: cacheresult, cdi, infinispan, injectedcacheresolver > Attachments: 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2015