March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7622) Hot Rod Rolling Upgrade throws TimeOutException

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7622?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7622: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Hot Rod Rolling Upgrade throws TimeOutException > ----------------------------------------------- > > Key: ISPN-7622 > URL: https://issues.jboss.org/browse/ISPN-7622 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR4 > > > When calling the {{synchonizeData}} operation, it timeouts after some minutes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7625) Make sure to report NoClassDefFoundError rather than hiding them as a ClassNotFoundException

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7625?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7625: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Make sure to report NoClassDefFoundError rather than hiding them as a ClassNotFoundException > -------------------------------------------------------------------------------------------- > > Key: ISPN-7625 > URL: https://issues.jboss.org/browse/ISPN-7625 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 9.0.0.CR4, 8.2.7.Final > > > I was having a {{NoClassDefFoundError}} caused by a module misconfiguration, but it turned out very complex to figure out as the only exception reported by Infinispan was about a misleading {{ClassNotFoundException}}. > I'm fixing the common classloading utility to make sure to log the errors appropriately. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7618) Bounded Off Heap can crash when a single entry size is larger than total size

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7618: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Bounded Off Heap can crash when a single entry size is larger than total size > ----------------------------------------------------------------------------- > > Key: ISPN-7618 > URL: https://issues.jboss.org/browse/ISPN-7618 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.CR4 > > > When looking into https://developer.jboss.org/thread/274297 we noticed sometimes that an indexed cache would cause OFF_HEAP to SEGFAULT. This wasn't identified in current stress tests. Need to confirm the cause. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7656) DefaultDataContainer.entrySet().stream().toArray(Object[]::new) may fail

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7656?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-7656: ------------------------------------- Even more fun the values method returns expired entries and doesn't even state that :( And since there is no metadata along with it the user wouldn't even know if it was expired or not. > DefaultDataContainer.entrySet().stream().toArray(Object[]::new) may fail > ------------------------------------------------------------------------ > > Key: ISPN-7656 > URL: https://issues.jboss.org/browse/ISPN-7656 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Assignee: William Burns > > When the default Spliterator estimates size of the array, it calls {{DefaultDataContainer.EntrySet#size()}} that returns directly the size of container (including expired entries). Then the container is iterated using {{ImmutableEntryIterator}} which excludes expired entries by default, and this may return less elements than the original size() provided. That causes failure like this: > {code} > java.lang.IllegalStateException: End size 1 is less than fixed size 2 > at java.util.stream.Nodes$FixedNodeBuilder.end(Nodes.java:1232) > at java.util.stream.Sink$ChainedReference.end(Sink.java:258) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:545) > at java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260) > at java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:438) > {code} > Note that this can also happen without expiration upon concurrent modification. We have to adjust the characteristics (remove {{#SIZED}}) of provided spliterators. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7611) Rename BackupWriteRcpCommand -> BackupWriteRpcCommand

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7611?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7611: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Rename BackupWriteRcpCommand -> BackupWriteRpcCommand > ----------------------------------------------------- > > Key: ISPN-7611 > URL: https://issues.jboss.org/browse/ISPN-7611 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Minor > Fix For: 9.0.0.CR4 > > > See the typo: BackupWriteR*cp*Command -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7619) Use dynamic timeout values in the PersistenceManagerCloseableSupplier

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7619?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7619: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Use dynamic timeout values in the PersistenceManagerCloseableSupplier > --------------------------------------------------------------------- > > Key: ISPN-7619 > URL: https://issues.jboss.org/browse/ISPN-7619 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.0.0.CR3 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR4 > > > When dealing with stores with large number on entries the hard-coded value of 10s may not be enough -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7610) TypeConverterDelegatingAdvancedCache.unboxEntryMap returns empty map

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7610?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7610: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > TypeConverterDelegatingAdvancedCache.unboxEntryMap returns empty map > -------------------------------------------------------------------- > > Key: ISPN-7610 > URL: https://issues.jboss.org/browse/ISPN-7610 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Radim Vansa > Assignee: William Burns > Fix For: 9.0.0.CR4 > > > When the unboxing is no-op, the entryMap is not modified, and the returned map is empty. > Please accompany the fix with a testcase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7571) Add a JDBC declarative test to the wildfly module integration tests

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7571?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7571: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Add a JDBC declarative test to the wildfly module integration tests > ------------------------------------------------------------------- > > Key: ISPN-7571 > URL: https://issues.jboss.org/browse/ISPN-7571 > Project: Infinispan > Issue Type: Task > Components: WildFly modules > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR4, 8.2.7.Final > > > The WidlFly modules it suite has a test for programmatic JDBC. Add a declarative test. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7594) Move memcached and websocket connectors out of the default configs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7594?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7594: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Move memcached and websocket connectors out of the default configs > ------------------------------------------------------------------ > > Key: ISPN-7594 > URL: https://issues.jboss.org/browse/ISPN-7594 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 9.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR4 > > > The memcached and websocket connectors are not as popular, so remove them from the default server config and ship additional examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7572) Infinispan initialization via DirectoryProvider can't use any CacheStore or other extensions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7572?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7572: ---------------------------------- Fix Version/s: 9.0.0.CR4 (was: 9.0.0.Final) > Infinispan initialization via DirectoryProvider can't use any CacheStore or other extensions > -------------------------------------------------------------------------------------------- > > Key: ISPN-7572 > URL: https://issues.jboss.org/browse/ISPN-7572 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Lucene Directory, WildFly modules > Affects Versions: 8.2.6.Final, 9.0.0.CR2 > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 9.0.0.CR4, 8.2.7.Final > > > When the Infinispan CacheManager is bootstrapped via Hibernate Search, the Infinispan modules are not necessarily visible to the deployment classpath (the TCCL). > In this case if the configuration file refers to any extension such as a {{CacheStore}}, Infinispan will fail to start as it doesn't depend on the modules of its extensions. > This will cause puzzling errors such as : > {{ISPN000327: Cannot find a parser for element 'string-keyed-jdbc-store' in namespace 'urn:infinispan:config:store:jdbc:8.0'. Check that your configuration is up-to date for this version of Infinispan.}} > For the record, the fact that the configuration parser expects to use the TCCL is an old problem which I've highlighted already in the past: > Explicit classloader support during parsing was introduced in 2013: > - http://lists.jboss.org/pipermail/infinispan-dev/2013-April/012590.html > Then removed again in 2014: > - http://lists.jboss.org/pipermail/infinispan-dev/2014-May/014952.html > I asked for improvements and hoped for someone to take ownership: > - http://lists.jboss.org/pipermail/infinispan-dev/2014-October/015549.html > In this last email I explained what Hibernate Search would do, in lack of better alternatives..and so we did. > Finally, this component of Hibernate Search code was transferred to the Infinispan repository so luckily we can change both components as you see most fit; the only requirement is to not expect the Hibernate users to have Infinispan on their TCCL. > My proposal is simple: the Infinispan-core module should have an optional dependency to its extensions, including at least all supported CacheStore implementations so that people can use them. > In fact, I expected them to do as it feels natural to have a graph edge towards extension points to be able to load them. > But [~NadirX] doesn't like that, so assigning the issue to him ;-) > Alternative ideas: > * allow people to mention module names explicitly in the Infinispan configuration? > * have a module which bootstraps the CacheManager, depending explicitly on all extensions, and register it over JNDI > I favour the second option, especially as it came up before as a dire pratical need for many other situations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017