February 2016 - infinispan-issues

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6099?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6099: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > 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, 8.2.0.Final > > 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-6214) Add configuration for initial number of nodes

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6214?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6214: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add configuration for initial number of nodes > --------------------------------------------- > > Key: ISPN-6214 > URL: https://issues.jboss.org/browse/ISPN-6214 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > It should be possible to specifiy a minimum number of nodes that need to belong to a cluster before the transport is considered "started". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6218) Make the ClusterRoleMapper use the InternalCacheRegistry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6218?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6218: ---------------------------------- Status: Open (was: New) > Make the ClusterRoleMapper use the InternalCacheRegistry > -------------------------------------------------------- > > Key: ISPN-6218 > URL: https://issues.jboss.org/browse/ISPN-6218 > Project: Infinispan > Issue Type: Task > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > The ClusterRoleMapper still relies on the ClusterRegistry. It should be ported to the InternalCacheRegistry -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6218) Make the ClusterRoleMapper use the InternalCacheRegistry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6218?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6218: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4016 > Make the ClusterRoleMapper use the InternalCacheRegistry > -------------------------------------------------------- > > Key: ISPN-6218 > URL: https://issues.jboss.org/browse/ISPN-6218 > Project: Infinispan > Issue Type: Task > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > The ClusterRoleMapper still relies on the ClusterRegistry. It should be ported to the InternalCacheRegistry -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6218) Make the ClusterRoleMapper use the InternalCacheRegistry

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6218: ------------------------------------- Summary: Make the ClusterRoleMapper use the InternalCacheRegistry Key: ISPN-6218 URL: https://issues.jboss.org/browse/ISPN-6218 Project: Infinispan Issue Type: Task Components: Core, Security Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.2.0.Beta2, 8.2.0.Final The ClusterRoleMapper still relies on the ClusterRegistry. It should be ported to the InternalCacheRegistry -- 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 Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6202?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6202: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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-6183) Initial state transfer fails with unexpected timeout

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6183?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6183: ------------------------------------- Assignee: Pedro Ruivo > Initial state transfer fails with unexpected timeout > ---------------------------------------------------- > > Key: ISPN-6183 > URL: https://issues.jboss.org/browse/ISPN-6183 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 7.2.5.Final > Environment: Java 7 on AWS EC2 > Reporter: Vladimir Dzhuvinov > Assignee: Pedro Ruivo > Attachments: default-jgroups-s3ping.xml, state-transfer-timeout-stack-trace.txt > > > Hi guys, > I would like to report a somewhat odd issue with initial state transfer. It was observed in two instances - an Infinispan 7.2.5 cluster with 2 nodes and an Infinispan 7.2.5 cluster with 6 nodes. The two clusters had been running for 2 weeks, the smaller for dev purposes with very light load - about a dozen cached objects. Upon adding an extra node an initial state transfer exception was encountered with both clusters, after about 4 minutes which is the default timeout setting for such situations. Several attempts were made to add a new node, incl. one with increased timeout (10 mins), but state transfer would still not complete, and throw an exception: > {code:java} > "message": "Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.Exception on object of type StateTransferManagerImpl", > "name": "org.infinispan.commons.CacheException", > "cause": { > "commonElementCount": 25, > "localizedMessage": "Initial state transfer timed out for cache authzStore.codeMap on ip-10-180-242-223-40643", > "message": "Initial state transfer timed out for cache authzStore.codeMap on ip-10-180-242-223-40643", > "name": "org.infinispan.commons.CacheException", > "extendedStackTrace": [ > { > "class": "org.infinispan.statetransfer.StateTransferManagerImpl", > "method": "waitForInitialStateTransferToComplete", > "file": "StateTransferManagerImpl.java", > "line": 222, > "exact": false, > "location": "StateTransferManagerImpl.class", > "version": "?" > }, > {code} > The JMX console reported "stateTransferInProgress=true" and "joinComplete=true". > The original clusters where then shut down and started again together with the new node, after which the clusters were successfully formed. > Attached is the exception stack trace and the JGroups config (based on the stock S3 ping). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6217) Create Javadocs for remote client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6217?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6217: ---------------------------------- Status: Open (was: New) > Create Javadocs for remote client > --------------------------------- > > Key: ISPN-6217 > URL: https://issues.jboss.org/browse/ISPN-6217 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation-Core > Affects Versions: 8.2.0.Beta2, 9.0.0.Final > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6215) Create Remote Java Client package

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6215?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6215: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Create Remote Java Client package > --------------------------------- > > Key: ISPN-6215 > URL: https://issues.jboss.org/browse/ISPN-6215 > Project: Infinispan > Issue Type: Task > Affects Versions: 8.2.0.Beta1 > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.2.0.Beta2, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6217) Create Javadocs for remote client

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6217: ----------------------------------------- Summary: Create Javadocs for remote client Key: ISPN-6217 URL: https://issues.jboss.org/browse/ISPN-6217 Project: Infinispan Issue Type: Feature Request Components: Documentation-Core Affects Versions: 8.2.0.Beta2, 9.0.0.Final Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Fix For: 9.0.0.Final -- 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