January 2017 - infinispan-issues - Jboss List Archives

[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)

9 years, 2 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] Tristan Tarrant edited comment on ISPN-7392 at 1/25/17 9:35 AM: ---------------------------------------------------------------- The fix I implemented, aside from correctly parsing policy attributes, enables no-anonymous implicitly if it has not been specified, as that is the expected behaviour. was (Author: nadirx): The fix I implemented for upstream, aside from correctly parsing policy attributes, enables no-anonymous implicitly if it has not been specified, as that is the expected behaviour. > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-7392: --------------------------------------- The fix I implemented for upstream, aside from correctly parsing policy attributes, enables no-anonymous implicitly if it has not been specified, as that is the expected behaviour. > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7228: ----------------------------------------- Assignee: (was: Vladimir Blagojevic) > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7228: ----------------------------------------- Assignee: Vladimir Blagojevic > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7228: ------------------------------------------- [~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles? > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7228: ------------------------------------------- [~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles? [1] https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec8858413006... > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7228: -------------------------------------- Comment: was deleted (was: [~NadirX] and [~anistor] I think this one goes to Adrian's turf. Adrian it seems that the [call|https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec88584...] to register protofiles from server subsystem does not propagate the exception back to the caller (in this case server subsystem). The exception is thus never caught and propagated back to us (admin console) through DMR which seems to be the ultimate cause of this JIRA issue. Would you please look at the stacktrace and see how we can fix this issue in registering protofiles? [1] https://github.com/infinispan/infinispan/blob/a535b9623504bc5ec8858413006...) > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7398) AbstractProtocolServerTest.testStartingWithoutTransport fails

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7398?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7398: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4802 > AbstractProtocolServerTest.testStartingWithoutTransport fails > ------------------------------------------------------------- > > Key: ISPN-7398 > URL: https://issues.jboss.org/browse/ISPN-7398 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR1 > > > Caused by ISPN-7066 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017