January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7393) Failed to properly start Hot Rod endpoint with the provided standalone-hotrod-ssl.xml

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7393?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7393: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR1 Resolution: Done > Failed to properly start Hot Rod endpoint with the provided standalone-hotrod-ssl.xml > ------------------------------------------------------------------------------------- > > Key: ISPN-7393 > URL: https://issues.jboss.org/browse/ISPN-7393 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.CR1 > > Attachments: keystore_client.jks, keystore_server.jks, truststore_client.jks, truststore_server.jks > > > {noformat} > 2017-01-24 15:20:57,033 INFO [org.infinispan.server.endpoint] (MSC service thread 1-6) DGENDPT10002: rest2 mapped to /rest > 2017-01-24 15:20:57,034 INFO [org.infinispan.server.endpoint] (MSC service thread 1-4) DGENDPT10002: rest1 mapped to /rest > 2017-01-24 15:20:57,080 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datagrid-infinispan-endpoint"), > ("router-connector" => "router") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => [ > "jboss.server.controller.management.security_realm.other", > "jboss.server.controller.management.security_realm.other2" > ], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.datagrid-infinispan-endpoint.router.router is missing [jboss.server.controller.management.security_realm.other2, jboss.server.controller.management.security_realm.other]"] > } > 2017-01-24 15:20:57,119 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.server.controller.management.security_realm.other (missing) dependents: [service jboss.datagrid-infinispan-endpoint.router.router] > service jboss.server.controller.management.security_realm.other2 (missing) dependents: [service jboss.datagrid-infinispan-endpoint.router.router] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7129) Duplicate cache names shouldn't be allowed

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7129?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7129: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.CR1 Resolution: Done > Duplicate cache names shouldn't be allowed > ------------------------------------------ > > Key: ISPN-7129 > URL: https://issues.jboss.org/browse/ISPN-7129 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 9.0.0.Alpha2 > Reporter: Jakub Markos > Assignee: Jakub Markos > Fix For: 9.0.0.CR1 > > > Multiple caches with the same name can be defined without a WARN/ERROR message. > It's also unclear which one will be used, for example with this configuration > {code} > <distributed-cache name="testCache"/> > <distributed-cache name="testCache"> > <eviction max-entries="100" /> > </distributed-cache> > <distributed-cache name="testCache"/> > {code} > -the cache with eviction will be used.- Actually the configurations are merged... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7400) Cache segment ownership information in DistributionManager

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7400: ---------------------------------- Summary: Cache segment ownership information in DistributionManager Key: ISPN-7400 URL: https://issues.jboss.org/browse/ISPN-7400 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 9.0.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Beta3 ISPN-7029 introduced {{DistributionInfo}} to simplify limit the number of times we compute the location of a given key. We can go further and cache the {{DistributionInfo}} of each segment in {{DistributionManager}}, so that each operation only needs to compute the segment of its key. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7370) Administration console - configuration of cache store is broken

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7370?page=com.atlassian.jira.plugin.... ] Roman Macor reopened ISPN-7370: ------------------------------- [~vblagojevic] I can reproduce this with both Beta2 and snapshot. > Administration console - configuration of cache store is broken > --------------------------------------------------------------- > > Key: ISPN-7370 > URL: https://issues.jboss.org/browse/ISPN-7370 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta3 > > Attachments: Screenshot from 2017-01-19.png > > > Click on cache container -> cache -> configuration -> Store -> Select store type e.g. Binary keyed JDBC store > Issues: > some property names are displayed like this: {{$ctrl.resolveFieldName()}} > ... links (for Write Behind for example) are not working > Please see the attached screenshot for details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7399) Make visitCommand return an Object instead of an InvocationStage

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7399?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7399: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4761 > Make visitCommand return an Object instead of an InvocationStage > ---------------------------------------------------------------- > > Key: ISPN-7399 > URL: https://issues.jboss.org/browse/ISPN-7399 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta3 > > > Replicated read benchmarks show a significant amount of time spent in {{BasicInvocationStage.toInvocationStage()}}. > We can make {{visitCommand}} return an {{Object}} instead of an {{InvocationStage}}, and that return value can be cast to an {{InvocationStage}} when a callback is needed. We can't call {{thenApply()}} etc. directly on an {{Object}}, but we can combine {{invokeNext(ctx, command).thenApply(function)}} into {{invokeNextThenApply(ctx, command, function)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7399) Make visitCommand return an Object instead of an InvocationStage

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7399?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7399: ------------------------------- Status: Open (was: New) > Make visitCommand return an Object instead of an InvocationStage > ---------------------------------------------------------------- > > Key: ISPN-7399 > URL: https://issues.jboss.org/browse/ISPN-7399 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta3 > > > Replicated read benchmarks show a significant amount of time spent in {{BasicInvocationStage.toInvocationStage()}}. > We can make {{visitCommand}} return an {{Object}} instead of an {{InvocationStage}}, and that return value can be cast to an {{InvocationStage}} when a callback is needed. We can't call {{thenApply()}} etc. directly on an {{Object}}, but we can combine {{invokeNext(ctx, command).thenApply(function)}} into {{invokeNextThenApply(ctx, command, function)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7397) Replace use of shared SingleFileStore with DummyInMemoryStore

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7397?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7397: ------------------------------- Description: ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. -Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. - was: ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. > Replace use of shared SingleFileStore with DummyInMemoryStore > ------------------------------------------------------------- > > Key: ISPN-7397 > URL: https://issues.jboss.org/browse/ISPN-7397 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. > -Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. - -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7397) Replace use of shared SingleFileStore with DummyInMemoryStore

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7397?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7397: ------------------------------- Description: ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. -Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. - The DummyInMemoryStore should be used instead. was: ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. -Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. - > Replace use of shared SingleFileStore with DummyInMemoryStore > ------------------------------------------------------------- > > Key: ISPN-7397 > URL: https://issues.jboss.org/browse/ISPN-7397 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. > -Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. - > The DummyInMemoryStore should be used instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7397) Replace use of shared SingleFileStore with DummyInMemoryStore

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7397?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-7397: ------------------------------- Summary: Replace use of shared SingleFileStore with DummyInMemoryStore (was: Create SharedSingleFileStore for testing) > Replace use of shared SingleFileStore with DummyInMemoryStore > ------------------------------------------------------------- > > Key: ISPN-7397 > URL: https://issues.jboss.org/browse/ISPN-7397 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > ISPN-7286 introduced the @Store annotation, which prevents non-shareable stores from being configured as shareable. The SingleFileStore is a non-shareable store, however its exploited by certain tests with its shared configuration set to true. With the introduction of @Store, the aforementioned tests now fail with an error stating that the SingleFileStore cannot be shared. > Therefore, it is necessary to create a SharedSingleFileStore solely for testing purposes which simply wraps the SingleFileStore and associated configurations, so that the existing tests which rely on a shared SingleFileStore do not fail. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7399) Make visitCommand return an Object instead of an InvocationStage

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7399: ---------------------------------- Summary: Make visitCommand return an Object instead of an InvocationStage Key: ISPN-7399 URL: https://issues.jboss.org/browse/ISPN-7399 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 9.0.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Beta3 Replicated read benchmarks show a significant amount of time spent in {{BasicInvocationStage.toInvocationStage()}}. We can make {{visitCommand}} return an {{Object}} instead of an {{InvocationStage}}, and that return value can be cast to an {{InvocationStage}} when a callback is needed. We can't call {{thenApply()}} etc. directly on an {{Object}}, but we can combine {{invokeNext(ctx, command).thenApply(function)}} into {{invokeNextThenApply(ctx, command, function)}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017