February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6202) Properties defined in <local-cache-configuration> are not applied to children

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6202?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6202: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4014, https://github.com/infinispan/infinispan/pull/4015 > Properties defined in <local-cache-configuration> are not applied to children > ----------------------------------------------------------------------------- > > Key: ISPN-6202 > URL: https://issues.jboss.org/browse/ISPN-6202 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.1.1.Final > Reporter: Sergey Sigelman > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta2, 8.2.0.Final, 8.1.2.Final > > > Configure Infinispan XML using <local-cache-configuration>: > {code:xml} > <local-cache-configuration name="defaultCacheConfig"> > .. attributes go here ... > </local-cache-configuration> > <local-cache name="testCache1" configuration="defaultCacheConfig" /> > {code} > "testCache1" does not inherit any attributes from "defaultCacheConfig". > org.infinispan.configuration.parsing.Parser80#getConfigurationBuilder finds and validates the supplied configuration, but does not actually apply it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6202) Properties defined in <local-cache-configuration> are not applied to children

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6202?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6202: ---------------------------------- Fix Version/s: 8.2.0.Beta2 8.2.0.Final 8.1.2.Final > Properties defined in <local-cache-configuration> are not applied to children > ----------------------------------------------------------------------------- > > Key: ISPN-6202 > URL: https://issues.jboss.org/browse/ISPN-6202 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.1.1.Final > Reporter: Sergey Sigelman > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta2, 8.2.0.Final, 8.1.2.Final > > > Configure Infinispan XML using <local-cache-configuration>: > {code:xml} > <local-cache-configuration name="defaultCacheConfig"> > .. attributes go here ... > </local-cache-configuration> > <local-cache name="testCache1" configuration="defaultCacheConfig" /> > {code} > "testCache1" does not inherit any attributes from "defaultCacheConfig". > org.infinispan.configuration.parsing.Parser80#getConfigurationBuilder finds and validates the supplied configuration, but does not actually apply it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6099) ConcurrentJoinTest random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6099?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6099: ------------------------------------ Yes, that should work. I *think* I managed to reproduce the problem with regular {{TCP}} once, but it's definitely easier to get with {{TCP_NIO2}}. Not sure why, at least in OpenJDK {{ServerSocketChannel}} and {{ServerSocket}} doesn't look that different. > ConcurrentJoinTest random failures > ---------------------------------- > > Key: ISPN-6099 > URL: https://issues.jboss.org/browse/ISPN-6099 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.1.0.Final > Environment: java version "1.8.0_60" > Java(TM) SE Runtime Environment (build 1.8.0_60-b27) > Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta2 > > Attachments: main.cpp > > > Since the switch to {{TCP_NIO2}} in the test suite, I've been seeing random failures in {{ConcurrentJoinTest}} and other tests that attempt to start multiple channels in parallel (e.g. {{StateTransferFunctionalTest}} and its subclasses). > Normally JGroups only reports a {{java.net.BindException: No available port to bind to in range [8000 .. 8099]}}, but I have modified {{org.jgroups.util.Util.createServerSocket()}} to report the cause exception and I got this: > {noformat} > java.net.BindException: No available port to bind to in range [8000 .. 8099] > at org.jgroups.util.Util.createServerSocketChannel(Util.java:3077) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.blocks.cs.NioServer.<init>(NioServer.java:86) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.protocols.TCP_NIO2.start(TCP_NIO2.java:97) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.JChannel.startStack(JChannel.java:890) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.JChannel._preConnect(JChannel.java:553) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.JChannel.connect(JChannel.java:288) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.jgroups.JChannel.connect(JChannel.java:279) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:199) ~[classes/:?] > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:190) ~[classes/:?] > at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) ~[?:?] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_60] > at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60] > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) ~[infinispan-commons-8.2.0-SNAPSHOT.jar:8.2.0-SNAPSHOT] > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:870) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:639) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:628) ~[classes/:?] > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:531) ~[classes/:?] > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:229) ~[classes/:?] > ... 11 more > Caused by: java.net.SocketException: Invalid argument > at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_60] > at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_60] > at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_60] > at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_60] > at java.nio.channels.ServerSocketChannel.bind(ServerSocketChannel.java:157) ~[?:1.8.0_60] > at org.jgroups.util.Util.createServerSocketChannel(Util.java:3072) ~[jgroups-3.6.7.Final.jar:3.6.7.Final] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6195) CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6195?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6195: ---------------------------------- Fix Version/s: 8.1.2.Final > CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel > ------------------------------------------------------------------------------------------ > > Key: ISPN-6195 > URL: https://issues.jboss.org/browse/ISPN-6195 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Fix For: 8.2.0.Beta2, 8.2.0.Final, 8.1.2.Final > > > Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors: > {code} > 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1) > ISPN000196: Failed to recover cluster state after the current node became the coordinator: > org.infinispan.commons.CacheException: Unsuccessful response received from node node2: > CacheNotFoundResponse > at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529) > at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387) > at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321) > at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5954) Adjust Embedded and Remote Uber Jar packaging

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5954?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5954: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta2 8.2.0.Final Resolution: Done > Adjust Embedded and Remote Uber Jar packaging > --------------------------------------------- > > Key: ISPN-5954 > URL: https://issues.jboss.org/browse/ISPN-5954 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > During the tests it turned out that both Remote and Embedded Uber Jars contains some classes which can not be loaded by JVM (because their dependencies are not there). This is not critical, but we should get rid of them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6081) Creating new cache with name that already exists leads to no response in the UI

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6081?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6081: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta2 8.2.0.Final Resolution: Done > Creating new cache with name that already exists leads to no response in the UI > ------------------------------------------------------------------------------- > > Key: ISPN-6081 > URL: https://issues.jboss.org/browse/ISPN-6081 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > Steps to reproduce: > Cache container detail page -> Add Cache -> fill in cache name and base configuration -> click Next -> click Create -> click Create on the following screen again > Result: There's an error in the server log but the console does not show any warning. The modal dialog stays open and users don't not know what happened unless they look at server logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6111) Management console - node view - total number of entries is not displayed

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6111?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6111: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta2 8.2.0.Final Resolution: Done > Management console - node view - total number of entries is not displayed > ------------------------------------------------------------------------- > > Key: ISPN-6111 > URL: https://issues.jboss.org/browse/ISPN-6111 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > Clusters tab -> click on cluster -> click on node > Node properties should include total number of entries. > e.g. Node #1 IP: 192.168.192.1 - 2,454 entries -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6077) AddCache dialog only offers cache templates from "clustered" cache container

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6077?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6077: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta2 8.2.0.Final Resolution: Done > AddCache dialog only offers cache templates from "clustered" cache container > ---------------------------------------------------------------------------- > > Key: ISPN-6077 > URL: https://issues.jboss.org/browse/ISPN-6077 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > When adding a new cache, the "Base configuration" element only shows options from a cache container named "clustered". If there are different cache containers in the configuration, the select element does not show anything. > The problem is getConfigurationTemplates function in infinispan-management-console/src/main/webapp/components/api/cache-creation-controller.service.js which should take into account different cache container names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3782) Update Infinispan code once HSEARCH-1461 is fixed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3782?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3782: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Thanks [~sannegrinovero]! > Update Infinispan code once HSEARCH-1461 is fixed > ------------------------------------------------- > > Key: ISPN-3782 > URL: https://issues.jboss.org/browse/ISPN-3782 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, JMX, reporting and management > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > We currently have a workaround for HSEARCH-1461 in ISPN-3335. > This should be undone once proper fix for HSEARCH-1461 exists in Hibernate Search. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3782) Update Infinispan code once HSEARCH-1461 is fixed

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3782?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-3782: ----------------------------------- Assignee: Sanne Grinovero (was: Adrian Nistor) > Update Infinispan code once HSEARCH-1461 is fixed > ------------------------------------------------- > > Key: ISPN-3782 > URL: https://issues.jboss.org/browse/ISPN-3782 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, JMX, reporting and management > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Sanne Grinovero > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > We currently have a workaround for HSEARCH-1461 in ISPN-3335. > This should be undone once proper fix for HSEARCH-1461 exists in Hibernate Search. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016