May 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10074) DefaultSegmentedDataContainer executeTask() and iterator() include expired entries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10074?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10074: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > DefaultSegmentedDataContainer executeTask() and iterator() include expired entries > ---------------------------------------------------------------------------------- > > Key: ISPN-10074 > URL: https://issues.jboss.org/browse/ISPN-10074 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.10.Final, 10.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > The {{executeTask()}} javadoc doesn't mention expired entries, but {{iterator()}}'s says they shouldn't be included, and non-segmented containers do not include them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10080) Test cache managers created in other threads cannot join the UDP cluster

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10080?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10080: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Test cache managers created in other threads cannot join the UDP cluster > ------------------------------------------------------------------------ > > Key: ISPN-10080 > URL: https://issues.jboss.org/browse/ISPN-10080 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.11.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > When a test wants to create a cache manager in another thread (e.g. with {{fork()}}) it should be able to call {{TestResourceTracker.testThreadStarted(this)}} and join the same cluster. > That works with TCP, but with UDP each thread gets its own multicast address and port, so multicast messages from one node don't reach the other. Unicast messages and {{TEST_PING}} do work. > This is the issue that made {{FunctionalTxTest}} fail in https://github.com/infinispan/infinispan/pull/6442 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10086) AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10086?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10086: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > AllClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures > ------------------------------------------------------------------------------ > > Key: ISPN-10086 > URL: https://issues.jboss.org/browse/ISPN-10086 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.11.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > When running tests in parallel, the remote request may complete before the thread that sent the request resumes. Because the scheduled executor is mocked to return {{null}}, this leads to a {{NullPointerException}}: > {noformat} > 09:43:41,995 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException > java.lang.NullPointerException: null > at org.infinispan.remoting.transport.AbstractRequest.setTimeoutFuture(AbstractRequest.java:94) ~[classes/:?] > at org.infinispan.remoting.transport.AbstractRequest.setTimeout(AbstractRequest.java:55) ~[classes/:?] > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeCommand(JGroupsTransport.java:831) ~[classes/:?] > at org.infinispan.manager.impl.AllClusterExecutor.submitConsumer(AllClusterExecutor.java:182) ~[classes/:?] > at org.infinispan.manager.ClusterExecutor.submitConsumer(ClusterExecutor.java:116) ~[classes/:?] > at org.infinispan.manager.Test$17.call(AllClusterExecutorTest.java:402) ~[test-classes/:?] > at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1601) ~[test-classes/:?] > at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:382) ~[test-classes/:?] > {noformat} > The problem may be that the test calls {{Mockito.verify()}} from the consumer twice, once for each node, instead of doing it only on the remote node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10095) Shared stores should throw exception when cache is local

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10095?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10095: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Shared stores should throw exception when cache is local > -------------------------------------------------------- > > Key: ISPN-10095 > URL: https://issues.jboss.org/browse/ISPN-10095 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.4.11.Final, 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > A shared store does not make sense with a local cache, therefore we should throw a {{CacheConfigurationException}} if configured. Due to assumptions elsewhere in the PersistenceManager, prior to this fix a NPE will be thrown during the Purge method of the store as {{transport == null}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10115) Missing persistence element when reading a template resource

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10115?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10115: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Missing persistence element when reading a template resource > ------------------------------------------------------------ > > Key: ISPN-10115 > URL: https://issues.jboss.org/browse/ISPN-10115 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > When reading a template resource, e.g via. > {code:java} > /subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS/local-cache-configuration=my-template:read-resource > {code} > The following is thrown: > {code:java} > [standalone@localhost:9990 /] /subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS/local-cache-configuration=my-template:read-resource > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datagrid-infinispan\"), > (\"cache-container\" => \"local\"), > (\"configurations\" => \"CONFIGURATIONS\"), > (\"local-cache-configuration\" => \"my-template\"), > (\"persistence\" => \"PERSISTENCE\") > ]' not found", > "rolled-back" => true > } > {code} > The problem is caused by the persistence=PERSISTENCE element not being created by the xml reader. This is now necessary as the aliases to the old store entries refer to {{persistence=PERSISTENCE/file-store}} etc, which is called during a read-resource operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10127) Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10127?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10127: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name > ------------------------------------------------------------------------------------------------ > > Key: ISPN-10127 > URL: https://issues.jboss.org/browse/ISPN-10127 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Environment: JDG 7.1.2 GA > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > An error message is returned when trying to get status of a site in JDG CLI, possibly because the site name has a hyphen character on it. > The following example of the site command being executed in CLI shows the response I've got, trying to execute in different ways: > {code:borderStyle=solid} > [standalone@localhost:9990 distributed-cache=default] site --status site-01 > line 1:14 mismatched input 'site' expecting set null > line 1:20 mismatched input '1' expecting set null > [standalone@localhost:9990 distributed-cache=default] site --status 'site-01' > Incorrect site name: 'site-01' > [standalone@localhost:9990 distributed-cache=default] site --status "site-01" > Incorrect site name: "site-01" > [standalone@localhost:9990 distributed-cache=default] site --status {site-01} > line 1:14 mismatched input '{' expecting set null > line 1:21 mismatched input '1' expecting set null > [standalone@localhost:9990 distributed-cache=default] site --status "{site-01}" > Incorrect site name: "{site-01}" > {code} > However, if I try to execute the following command with a site name without the hyphen character in it's value, everything works as expected: > {code:borderStyle=solid} > [standalone@localhost:9990 distributed-cache=default] site --status SFO > online > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10129) CLI NullPointerException after running CLI "create" command

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10129?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10129: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > CLI NullPointerException after running CLI "create" command > ----------------------------------------------------------- > > Key: ISPN-10129 > URL: https://issues.jboss.org/browse/ISPN-10129 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Environment: JDG-7.3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Getting Null Pointer Exception after running "create" command from CLI : > Below is the exception snippet : > ~~~ > 16:59:43,111 ERROR [org.infinispan.cli.interpreter.Interpreter] (management-handler-thread - 1) ISPN019003: Interpreter error: java.lang.NullPointerException > at org.infinispan.cli.interpreter.session.SessionImpl.createCache(SessionImpl.java:109) > at org.infinispan.cli.interpreter.statement.CreateStatement.execute(CreateStatement.java:25) > at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:140) > at org.infinispan.server.infinispan.SecurityActions.lambda$executeInterpreter$7(SecurityActions.java:268) > at org.infinispan.security.Security.doPrivileged(Security.java:57) > at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:77) > at org.infinispan.server.infinispan.SecurityActions.executeInterpreter(SecurityActions.java:269) > at org.jboss.as.clustering.infinispan.subsystem.CliInterpreterHandler.execute(CliInterpreterHandler.java:71) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:265) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:231) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:246) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > ~~~ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10142) Wildfly modules integrationtests ignore branding

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10142?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10142: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Wildfly modules integrationtests ignore branding > ------------------------------------------------ > > Key: ISPN-10142 > URL: https://issues.jboss.org/browse/ISPN-10142 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_failure > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > {{standalone-test.xml}} uses module {{org.infinispan.extension:ispn-${infinispan.core.schema.version}}}, ignoring the branding. The module name should be {{org.infinispan.extension:${infinispan.module.slot}}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10155) Counter manager configs not applied on server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10155?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10155: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Counter manager configs not applied on server > --------------------------------------------- > > Key: ISPN-10155 > URL: https://issues.jboss.org/browse/ISPN-10155 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter, Server > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Labels: rhdemo-2019 > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > The server model for the counter manager is not correctly set up: > * attributes are registered as metrics > * the add handler ignores attributes > * the configurationmanager is not actually configured > * the xml writer attempts to serialize attributes from the wrong model nodes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10165) Fix rolling upgrades tests according to latest changes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10165?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10165: ----------------------------------- Fix Version/s: 9.4.14.Final (was: 9.4.13.Final) > Fix rolling upgrades tests according to latest changes > ------------------------------------------------------ > > Key: ISPN-10165 > URL: https://issues.jboss.org/browse/ISPN-10165 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Currently the rolling upgrades tests are not running properly (as of JDK11 changes were introduced, etc). > Fix the rolling upgrades related testsuite to work properly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2019