February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-7512) Add FRAG3 back to TCP configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7512?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7512: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > Add FRAG3 back to TCP configuration > ----------------------------------- > > Key: ISPN-7512 > URL: https://issues.jboss.org/browse/ISPN-7512 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7519) NPE and Deadlock during server start

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7519?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7519: ------------------------------------ Attachment: surefire-trace.txt > NPE and Deadlock during server start > ------------------------------------ > > Key: ISPN-7519 > URL: https://issues.jboss.org/browse/ISPN-7519 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite - Server > Affects Versions: 9.0.0.CR1 > Reporter: Gustavo Fernandes > Attachments: server-trace.txt, surefire-trace.txt > > > When running the full test suite, it deadlocked when running the test {{StateTransferSuppressIT.testRebalanceWithFirstNodeStop}}. > The server startup printed > {noformat} > 12:13:07,787 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Ruppaner' 9.0.0-SNAPSHOT > 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) DGISPN0001: Started memcachedCache cache from clustered container > 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) DGISPN0001: Started default cache from clustered container > 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10000: MemcachedServer starting > 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10000: HotRodServer starting > 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211 > 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222 > 12:13:08,188 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10000: REST starting > 12:13:08,259 WARNING [io.netty.channel.epoll.EpollEventLoop] (MemcachedServerMaster-1-1) Unexpected exception in the selector loop.: java.lang.NullPointerException > at io.netty.util.internal.shaded.org.jctools.queues.MpscChunkedArrayQueue.poll(MpscChunkedArrayQueue.java:264) > at io.netty.util.concurrent.SingleThreadEventExecutor.pollTaskFrom(SingleThreadEventExecutor.java:223) > at io.netty.util.concurrent.SingleThreadEventExecutor.pollTask(SingleThreadEventExecutor.java:218) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:408) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:306) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) > at java.lang.Thread.run(Thread.java:745) > 12:13:08,338 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-1) ISPN012003: REST server starting, listening on 127.0.0.1:8080 > 12:13:08,338 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10002: REST mapped to /rest > {noformat} > and then hanged. Attached is the stack trace of the server, and the forked test process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7519) NPE and Deadlock during server start

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7519?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7519: ------------------------------------ Attachment: server-trace.txt > NPE and Deadlock during server start > ------------------------------------ > > Key: ISPN-7519 > URL: https://issues.jboss.org/browse/ISPN-7519 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite - Server > Affects Versions: 9.0.0.CR1 > Reporter: Gustavo Fernandes > Attachments: server-trace.txt > > > When running the full test suite, it deadlocked when running the test {{StateTransferSuppressIT.testRebalanceWithFirstNodeStop}}. > The server startup printed > {noformat} > 12:13:07,787 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Ruppaner' 9.0.0-SNAPSHOT > 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) DGISPN0001: Started memcachedCache cache from clustered container > 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) DGISPN0001: Started default cache from clustered container > 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10000: MemcachedServer starting > 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10000: HotRodServer starting > 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211 > 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222 > 12:13:08,188 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10000: REST starting > 12:13:08,259 WARNING [io.netty.channel.epoll.EpollEventLoop] (MemcachedServerMaster-1-1) Unexpected exception in the selector loop.: java.lang.NullPointerException > at io.netty.util.internal.shaded.org.jctools.queues.MpscChunkedArrayQueue.poll(MpscChunkedArrayQueue.java:264) > at io.netty.util.concurrent.SingleThreadEventExecutor.pollTaskFrom(SingleThreadEventExecutor.java:223) > at io.netty.util.concurrent.SingleThreadEventExecutor.pollTask(SingleThreadEventExecutor.java:218) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:408) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:306) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) > at java.lang.Thread.run(Thread.java:745) > 12:13:08,338 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-1) ISPN012003: REST server starting, listening on 127.0.0.1:8080 > 12:13:08,338 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10002: REST mapped to /rest > {noformat} > and then hanged. Attached is the stack trace of the server, and the forked test process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7519) NPE and Deadlock during server start

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7519: --------------------------------------- Summary: NPE and Deadlock during server start Key: ISPN-7519 URL: https://issues.jboss.org/browse/ISPN-7519 Project: Infinispan Issue Type: Bug Components: Server, Test Suite - Server Affects Versions: 9.0.0.CR1 Reporter: Gustavo Fernandes When running the full test suite, it deadlocked when running the test {{StateTransferSuppressIT.testRebalanceWithFirstNodeStop}}. The server startup printed {noformat} 12:13:07,787 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Ruppaner' 9.0.0-SNAPSHOT 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) DGISPN0001: Started memcachedCache cache from clustered container 12:13:08,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) DGISPN0001: Started default cache from clustered container 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10000: MemcachedServer starting 12:13:08,181 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10000: HotRodServer starting 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211 12:13:08,182 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222 12:13:08,188 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10000: REST starting 12:13:08,259 WARNING [io.netty.channel.epoll.EpollEventLoop] (MemcachedServerMaster-1-1) Unexpected exception in the selector loop.: java.lang.NullPointerException at io.netty.util.internal.shaded.org.jctools.queues.MpscChunkedArrayQueue.poll(MpscChunkedArrayQueue.java:264) at io.netty.util.concurrent.SingleThreadEventExecutor.pollTaskFrom(SingleThreadEventExecutor.java:223) at io.netty.util.concurrent.SingleThreadEventExecutor.pollTask(SingleThreadEventExecutor.java:218) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:408) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:306) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) at java.lang.Thread.run(Thread.java:745) 12:13:08,338 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-1) ISPN012003: REST server starting, listening on 127.0.0.1:8080 12:13:08,338 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10002: REST mapped to /rest {noformat} and then hanged. Attached is the stack trace of the server, and the forked test process. -- 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 Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7433?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7433: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/4828, https://github.com/infinispan/infinispan/pull/4890 (was: https://github.com/infinispan/infinispan/pull/4828) > 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.CR2 > > > 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-7510) Upgrade to protostream-4.0.0.Alpha7

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7510?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7510: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to protostream-4.0.0.Alpha7 > ----------------------------------- > > Key: ISPN-7510 > URL: https://issues.jboss.org/browse/ISPN-7510 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7511) DummyInMemoryStore warnings in the testsuite

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7511?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7511: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > DummyInMemoryStore warnings in the testsuite > -------------------------------------------- > > Key: ISPN-7511 > URL: https://issues.jboss.org/browse/ISPN-7511 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.CR2 > > > The DummyInMemoryStoreConfiguration incorrectly passes the DummyInMemoryStore class as part of its attribute definition set, this leads to "ISPN000437 Unable to validate DummyInMemoryStore with the implementing store as the @ConfigurationFor annotation is missing". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7516) DeployedStoreConfiguration always warns missing @ConfigurationFor annotation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7516?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7516: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR2 Resolution: Done > DeployedStoreConfiguration always warns missing @ConfigurationFor annotation > ---------------------------------------------------------------------------- > > Key: ISPN-7516 > URL: https://issues.jboss.org/browse/ISPN-7516 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 9.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.CR2 > > > Warnings [1] appear on the server when the DeployedStoreConfigurationBuilder is utilised as the DeployedStoreConfiguration utilises a class name, opposed to a class object, so it is not possible to check the annotations of the store in this case. Therefore, we should skip these checks as they will always fail. > [1] "ISPN000437 Unable to validate AbstractStoreConfiguration with the implementing store as the @ConfigurationFor annotation is missing". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7518) All Infinispan jars are shipped with GNU license instead of ASL

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7518?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7518: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > All Infinispan jars are shipped with GNU license instead of ASL > --------------------------------------------------------------- > > Key: ISPN-7518 > URL: https://issues.jboss.org/browse/ISPN-7518 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 9.0.0.CR1, 8.2.6.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR2, 8.2.7.Final > > > Resulting from the fact that infinispan-licence is missing in the maven build modules and the parent pom references a static version "1" which has never been updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6673: -------------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4467, https://github.com/infinispan/infinispan/pull/4889 (was: https://github.com/infinispan/infinispan/pull/4467) > Implement Rolling Upgrades with Kubernetes > ------------------------------------------ > > Key: ISPN-6673 > URL: https://issues.jboss.org/browse/ISPN-6673 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > There are 2 mechanisms which seems to do the same but are totally different: > * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon > * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration > Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. -- 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