March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7567) ClusterListenerDistInitialStateTest.testPrimaryOwnerGoesDownAfterSendingEvent random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7567?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7567: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) Resolution: Done > ClusterListenerDistInitialStateTest.testPrimaryOwnerGoesDownAfterSendingEvent random failures > --------------------------------------------------------------------------------------------- > > Key: ISPN-7567 > URL: https://issues.jboss.org/browse/ISPN-7567 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.0.CR3 > > > Fixes this failure: > {code:java} > java.lang.AssertionError: expected [ClusterListenerDistTest-NodeC-8233] but found [ClusterListenerDistTest-NodeA-44676] > at org.infinispan.notifications.cachelistener.cluster.AbstractClusterListenerNonTxTest.testPrimaryOwnerGoesDownAfterSendingEvent(AbstractClusterListenerNonTxTest.java:80) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7570) Administration console - task execution tab should be removed in standalone non-clustered mode

by Roman Macor (JIRA)

Roman Macor created ISPN-7570: --------------------------------- Summary: Administration console - task execution tab should be removed in standalone non-clustered mode Key: ISPN-7570 URL: https://issues.jboss.org/browse/ISPN-7570 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.CR2 Reporter: Roman Macor Tasks cannot be performed on a server in standalone non-clustered mode, that's why there is no "Tasks" tab, in the cache container configuration. Task execution tab in cache container should also be removed. Currently, there is launch new task button, under this tab, but it doesn't do anything. Note: This works correctly in domain mode and standalone clustered mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7569) Administration console - Creating node with existing name does not show error

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7569?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-7569: ------------------------------ Summary: Administration console - Creating node with existing name does not show error (was: Administration console - Creating node with existing name does not shows error) > Administration console - Creating node with existing name does not show error > ----------------------------------------------------------------------------- > > Key: ISPN-7569 > URL: https://issues.jboss.org/browse/ISPN-7569 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > > Try creating node with the same name as one of the existing nodes e.g. server-one > Result: there is a loading screen for a moment, node is not created, no error message is shown > Expected result: there should be error message saying node with the specified name already exists -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7569) Administration console - Creating node with existing name does not shows error

by Roman Macor (JIRA)

Roman Macor created ISPN-7569: --------------------------------- Summary: Administration console - Creating node with existing name does not shows error Key: ISPN-7569 URL: https://issues.jboss.org/browse/ISPN-7569 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.CR2 Reporter: Roman Macor Try creating node with the same name as one of the existing nodes e.g. server-one Result: there is a loading screen for a moment, node is not created, no error message is shown Expected result: there should be error message saying node with the specified name already exists -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6039) NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6039?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6039: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) Resolution: Done > NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite random failures > --------------------------------------------------------------------------------------------------- > > Key: ISPN-6039 > URL: https://issues.jboss.org/browse/ISPN-6039 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Blocker > Labels: testsuite_stability > Fix For: 9.0.0.CR3 > > > The problem is that the state transfer write can happen after we started the regular put, and is blocked by the {{BlockingInterceptor}}. The test then unblocks the state transfer put, but never unblocks the regular put, which eventually times out. > {noformat} > java.util.concurrent.TimeoutException > at java.util.concurrent.FutureTask.get(FutureTask.java:205) > at org.infinispan.distribution.rehash.NonTxBackupOwnerBecomingPrimaryOwnerTest.doTest(NonTxBackupOwnerBecomingPrimaryOwnerTest.java:193) > at org.infinispan.distribution.rehash.NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite(NonTxBackupOwnerBecomingPrimaryOwnerTest.java:75) > {noformat} > The test should be more explicit about the state transfer put - ideally it should have 2 cases, one with the state transfer put happening before the regular put, and one after. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7459) Unable to create new cache as default configuration is always null.

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7459?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7459: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 Resolution: Done > Unable to create new cache as default configuration is always null. > ------------------------------------------------------------------- > > Key: ISPN-7459 > URL: https://issues.jboss.org/browse/ISPN-7459 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Server > Affects Versions: 9.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.CR3 > > > This is because `org.jboss.as.clustering.infinispan.DefaultCacheContainer` still passes null when creating the `DefaultCacheManager` -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7564) Upgrade to Log4j2 2.8.1

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7564?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7564: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) Resolution: Done > Upgrade to Log4j2 2.8.1 > ----------------------- > > Key: ISPN-7564 > URL: https://issues.jboss.org/browse/ISPN-7564 > Project: Infinispan > Issue Type: Component Upgrade > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.CR3 > > > ISPN-7563 requires at least Log4j2 2.6, because Netty uses some of the new {{Logger}} overloads that avoid creating a varargs array. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7566) ByteString.readObject() throws NegativeArraySizeException when length > 127

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7566?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7566: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) Resolution: Done > ByteString.readObject() throws NegativeArraySizeException when length > 127 > --------------------------------------------------------------------------- > > Key: ISPN-7566 > URL: https://issues.jboss.org/browse/ISPN-7566 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.CR3 > > > We don't expect or recommend cache names this big, but we should fail at the time the `ByteString` is created and not at the time it is read by a remote node. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7563) Netty should use Log4j2

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7563?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7563: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) Resolution: Done > Netty should use Log4j2 > ----------------------- > > Key: ISPN-7563 > URL: https://issues.jboss.org/browse/ISPN-7563 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.CR3 > > > {{NettyTransport}} calls {{InternalLoggerFactory.setDefaultFactory(new io.netty.util.internal.logging.Log4JLoggerFactory())}}, which uses Log4j 1.2.x. > It should use {{Log4j2LoggerFactory}} instead, so that Netty uses the same logging configuration as Infinispan. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7556) Decoder2x.readOptionalParams should not call markReaderIndex()

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7556?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7556: -------------------------------------- Fix Version/s: 9.0.0.CR3 (was: 9.0.0.Final) > Decoder2x.readOptionalParams should not call markReaderIndex() > -------------------------------------------------------------- > > Key: ISPN-7556 > URL: https://issues.jboss.org/browse/ISPN-7556 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.CR3 > > > {{Decoder2x.readOptionalParams()}} calls {{buffer.markReaderIndex()}} after reading each parameter, but doesn't save the parameters anywhere. That means if the buffer doesn't contain all the parameters, the decode pass ends unsuccessfully, and the next decode pass doesn't see the parameters read by the previous pass. > Higher-level methods like {{Decoder2x.readMaybeNamedFactory()}} also call {{readOptionalParams()}} without saving their own state first, meaning their state can be lost as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017