February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7401) AbstractProtocolServer relying on startDefaultCache

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7401?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7401: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > AbstractProtocolServer relying on startDefaultCache > --------------------------------------------------- > > Key: ISPN-7401 > URL: https://issues.jboss.org/browse/ISPN-7401 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR3 > > > The {{AbstractProtocolServer}} class is used/extended by various other tools, including testing infrastructure of OGM. > It currently is "booting" the system by starting the default cache. This concept needs an update. > See {{org.infinispan.server.core.AbstractProtocolServer.startDefaultCache()}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7517) Investigate Netty's "Too many open files" exception in testing of infinispan-compatibility-mode-it

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7517?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7517: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Investigate Netty's "Too many open files" exception in testing of infinispan-compatibility-mode-it > -------------------------------------------------------------------------------------------------- > > Key: ISPN-7517 > URL: https://issues.jboss.org/browse/ISPN-7517 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Reporter: Sanne Grinovero > Fix For: 9.0.0.CR3 > > > See also discussion on ML: > - http://lists.jboss.org/pipermail/infinispan-dev/2017-February/017232.html > Running: > {noformat} > mci -rf :infinispan-compatibility-mode-it > {noformat} > {noformat} > Failed tests: > ByteArrayKeyDistEmbeddedHotRodTest.setup:27 » IllegalState failed to create a ... > ByteArrayKeyReplEmbeddedHotRodTest.setup:87 » IllegalState failed to create a ... > ByteArrayValueDistEmbeddedHotRodTest.setup:27 » IllegalState failed to create ... > ByteArrayValueReplEmbeddedHotRodTest.setup:87 » IllegalState failed to create ... > DistEmbeddedRestHotRodTest.setup:25 » IllegalState failed to create a child ev... > DistL1EmbeddedHotRodTest.setup:30 » IllegalState failed to create a child even... > DistMemcachedEmbeddedTest.setup:39 » IllegalState failed to create a child eve... > org.infinispan.it.compatibility.EmbeddedHotRodCacheListenerTest.setup(org.infinispan.it.compatibility.EmbeddedHotRodCacheListenerTest) > Run 1: EmbeddedHotRodCacheListenerTest.setup:36 » IllegalState failed to create a chi... > Run 2: PASS > Run 3: PASS > EmbeddedHotRodTest.testEventFilteringStatic:274->lambda$testEventFilteringStatic$4:276 » Transport > EmbeddedMemcachedCacheListenerTest.setup:39 » IllegalState failed to create a ... > EmbeddedRestMemcachedHotRodTest.setup:50 » IllegalState failed to create a chi... > ReplEmbeddedRestHotRodTest.setup:38 » IllegalState failed to create a child ev... > Tests run: 101, Failures: 12, Errors: 0, Skipped: 47 > {noformat} > Errors are all about a similar stacktrace. > {noformat} > java.lang.IllegalStateException: failed to create a child event loop > at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:88) > at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:58) > at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:51) > at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:87) > at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:82) > at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:63) > at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:51) > at org.jboss.resteasy.plugins.server.netty.NettyJaxrsServer.start(NettyJaxrsServer.java:239) > at org.infinispan.rest.NettyRestServer.start(NettyRestServer.java:81) > at org.infinispan.it.compatibility.CompatibilityCacheFactory.createRestCache(CompatibilityCacheFactory.java:199) > at org.infinispan.it.compatibility.CompatibilityCacheFactory.createRestMemcachedCaches(CompatibilityCacheFactory.java:137) > at org.infinispan.it.compatibility.CompatibilityCacheFactory.setup(CompatibilityCacheFactory.java:123) > at org.infinispan.it.compatibility.DistMemcachedEmbeddedTest.setup(DistMemcachedEmbeddedTest.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > Caused by: io.netty.channel.ChannelException: failed to open a new selector > at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:157) > at io.netty.channel.nio.NioEventLoop.<init>(NioEventLoop.java:148) > at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:126) > at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:36) > at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:84) > ... 32 more > Caused by: java.io.IOException: Too many open files > at sun.nio.ch.EPollArrayWrapper.epollCreate(Native Method) > at sun.nio.ch.EPollArrayWrapper.<init>(EPollArrayWrapper.java:130) > at sun.nio.ch.EPollSelectorImpl.<init>(EPollSelectorImpl.java:69) > at sun.nio.ch.EPollSelectorProvider.openSelector(EPollSelectorProvider.java:36) > at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:155) > ... 36 more > {noformat} > N.B. > The failure is quite consistent on my workstation, almost always results in the same tests failing. Yet occasionally they all pass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7509) TotalOrderStateTransferInterceptor doesn't handle OutdatedTopologyException for read commands

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7509?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7509: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > TotalOrderStateTransferInterceptor doesn't handle OutdatedTopologyException for read commands > --------------------------------------------------------------------------------------------- > > Key: ISPN-7509 > URL: https://issues.jboss.org/browse/ISPN-7509 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.CR3 > > > Since ISPN-6859, read commands can also trigger {{OutdatedTopologyException}}, but these are only handled in the non-TO {{StateTransferInterceptor}}. When a read should be retried because of a topology change in a TO cache, the {{OutdatedTopologyException}} is instead thrown to the user: > {noformat} > 16:50:40,595 DEBUG (jgroups-9,Test-NodeA-483:[]) [InvocationContextInterceptor] ISPN000311: Received a command from an outdated topology, returning the exception to caller > org.infinispan.statetransfer.OutdatedTopologyException: Did not get any successful response, got {Test-NodeC-46564=UnsuccessfulResponse} > 16:50:40,595 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.totalorder.statetransfer.DistTotalOrderVersionedStateTransferTest.testStateTransfer > org.infinispan.statetransfer.OutdatedTopologyException: Did not get any successful response, got {Test-NodeC-46564=UnsuccessfulResponse} > {noformat} > This causes random failures in {{DistTotalOrderVersionedStateTransferTest}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7477) Endpoints with non-default names are not parsed

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7477?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7477: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Endpoints with non-default names are not parsed > ------------------------------------------------ > > Key: ISPN-7477 > URL: https://issues.jboss.org/browse/ISPN-7477 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.CR3 > > Attachments: domain.xml > > > When we parse endpoints from DMR we assume that they have certain names. In addition, we can not parse multiple endpoints of the same type (hotrod, rest etc) and finally we assume that they belong to a certain container which might not be the case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7433) Investigate performance with different xmit_interval values

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7433?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7433: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Investigate performance with different xmit_interval values > ----------------------------------------------------------- > > Key: ISPN-7433 > URL: https://issues.jboss.org/browse/ISPN-7433 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: performance > Fix For: 9.0.0.CR3 > > > The default {{UNICAST3.xmit_interval}} is 500ms, and the default {{NAKACK2.xmit_interval}} is 1000ms. According to Bela, a {{xmit_interval}} of 100ms should be much better for performance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7524) PutKeyValueCommand.toString should contain commandInvocationId

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7524?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7524: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > PutKeyValueCommand.toString should contain commandInvocationId > -------------------------------------------------------------- > > Key: ISPN-7524 > URL: https://issues.jboss.org/browse/ISPN-7524 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.CR3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7465) Using template overrides cache definition

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7465?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7465: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Using template overrides cache definition > ----------------------------------------- > > Key: ISPN-7465 > URL: https://issues.jboss.org/browse/ISPN-7465 > Project: Infinispan > Issue Type: Bug > Reporter: William Burns > Fix For: 9.0.0.CR3 > > > When using the `getCache(String cacheName, String configurationName);` method. If a cache is defined with that name it only uses the template and will ignore the defined configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7415) Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7415?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7415: ------------------------------ Fix Version/s: 9.0.0.CR3 (was: 9.0.0.CR2) > Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata > -------------------------------------------------------------------------- > > Key: ISPN-7415 > URL: https://issues.jboss.org/browse/ISPN-7415 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.CR3 > > > The default lifespan and maxIdle are -1 to signal no expiration, but calling {{EmbeddedMetadata.Builder.lifespan\(x)}} with any value will make it create an {{EmbeddedExpirableMetadata}} instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7522) LocalMode[No]PassivationTest fails randomly

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7522?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7522: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > LocalMode[No]PassivationTest fails randomly > ------------------------------------------- > > Key: ISPN-7522 > URL: https://issues.jboss.org/browse/ISPN-7522 > Project: Infinispan > Issue Type: Bug > Components: Core, Eviction, Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.CR2 > > > LocalModePassivationTest and LocalModeNoPassivationTest can fail randomly saying entries aren't present. All entries should be present since there is a configured store, this is a pretty big loss of data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7503) Endpoint subsystem doesn't resolve expressions

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7503?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7503: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Endpoint subsystem doesn't resolve expressions > ---------------------------------------------- > > Key: ISPN-7503 > URL: https://issues.jboss.org/browse/ISPN-7503 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR2 > > > The endpoint subsystem doesn't use the expression resolver to evaluate resource attributes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017