January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7334) Administration console - clicking on Caches tab shortly after logging in shows error pop up

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7334?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic edited comment on ISPN-7334 at 1/26/17 5:39 AM: -------------------------------------------------------------------- [~rmacor] I think we should not worry too much about these kinds of issues (not being able to reproduce by a human user). I tried repeatedly to reproduce and I could never do so. It is likely related to rendering and setup of link routes for Caches tab. Very little we can do here and I suggest we close this issue. was (Author: vblagojevic): [~rmacor] I think we should not worry too much about these kinds of issues (not being able to reproduce by a human user). I tried repeatedly to reproduce and I could never do so. It is likely related to rendering and setup of link routes for the link. Very little we can do here and I suggest we close this issue. > Administration console - clicking on Caches tab shortly after logging in shows error pop up > ------------------------------------------------------------------------------------------- > > Key: ISPN-7334 > URL: https://issues.jboss.org/browse/ISPN-7334 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: Screenshot from 2017-01-04.png > > > This happens in our test suite in standalone mode. > Steps to reproduce (might be difficult without a script): > log in -> click on Caches tab immediately (doesn't occur if we wait 200 milliseconds between logging and clicking on Caches tab) > Result: > error pop up with empty message "{}" > Please see the attached screen shot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6421) Instantiation of cache based on template should not modify template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6421?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6421: ------------------------------------------- Ok [~ryanemerson] I tried this myself and concluded that we are properly handling this use case just as you described. Closing this issue. > Instantiation of cache based on template should not modify template > ------------------------------------------------------------------- > > Key: ISPN-6421 > URL: https://issues.jboss.org/browse/ISPN-6421 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 9.0.0.CR1, 9.0.0.Final > > > In cache add, instiating a cache A based on template T should not modify T but should create a configuration A under configurations=CONFIGURATIONS with the "template" attribute set to false and the "configuration" attribute set to T and then a cache A with "configuration" A. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6421) Instantiation of cache based on template should not modify template

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6421?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic resolved ISPN-6421. --------------------------------------- Resolution: Done > Instantiation of cache based on template should not modify template > ------------------------------------------------------------------- > > Key: ISPN-6421 > URL: https://issues.jboss.org/browse/ISPN-6421 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 9.0.0.CR1, 9.0.0.Final > > > In cache add, instiating a cache A based on template T should not modify T but should create a configuration A under configurations=CONFIGURATIONS with the "template" attribute set to false and the "configuration" attribute set to T and then a cache A with "configuration" A. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7370?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7370: ------------------------------------------- Ok [~rmacor] please give the exact steps starting with a clean/fresh server. I tried and tried, but could not reproduce it. > 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.CR1 > > 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)

8 years, 11 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: ------------------------------------------- [~anistor] I get it! However, we don't have methods getFileErrors and getFilesWithErrors exposed to DMR, hence our hands are tied. Until we do, there is little [~ryanemerson] and I can do here. [~anistor] can you perhaps expose an operation that would check syntax and semantic errors of a registered protobuf? That way we can register proto but and then query if there are any errors. What would also work changing the semantics of registerProtofile/Schema so we can get these errors returned right away but I am not sure what is the impact of such a change and/or if it is doable. Thoughts [~anistor] and [~NadirX]? > 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)

8 years, 11 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-7228: ------------------------------------- ProtobufMetadataManager's javadoc is unfortunatelly wrong. Method registerProtofiles fails with exception only if the registration did not happen at all due to whatever unlikely cache failure. Syntax or semantic errors in the file do not cause the registration to fail with exception. The file is still written to the cache. getFileErrors and getFilesWithErrors methods should be used to determine if there are syntax or semantic errors. Please note that due to imports you could have an error in a completely different file than the one updated. > 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)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7401) AbstractProtocolServer relying on startDefaultCache

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-7401: ------------------------------------- Summary: AbstractProtocolServer relying on startDefaultCache Key: ISPN-7401 URL: https://issues.jboss.org/browse/ISPN-7401 Project: Infinispan Issue Type: Task Components: Server Reporter: Sanne Grinovero Assignee: Tristan Tarrant Fix For: 9.0.0.CR1 The {{AbstractProtocolServer}} class is used/extended by various other tools, including testing infrastructure of OGM. It currently is "booting" the system by starting the default cache. This concept needs an update. See {{org.infinispan.server.core.AbstractProtocolServer.startDefaultCache()}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7327) Backports for 8.2.7.Final

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-7327?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-7327: ------------------------------- Priority: Blocker (was: Major) > Backports for 8.2.7.Final > ------------------------- > > Key: ISPN-7327 > URL: https://issues.jboss.org/browse/ISPN-7327 > Project: Infinispan > Issue Type: Task > Affects Versions: 8.2.5.Final, 8.2.6.Final > Reporter: Paul Ferraro > Priority: Blocker > Fix For: 8.2.7.Final > > > Tracking JIRA for issues to be backported to 8.2.x for 8.2.7.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7400?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7400: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4804 > 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 > Labels: performance > Fix For: 9.0.0.CR1 > > > 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)

8 years, 11 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7400?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7400: ------------------------------- Status: Open (was: New) > 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 > Labels: performance > Fix For: 9.0.0.CR1 > > > 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)

8 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 January 2017