April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6566) Segment information available for Cache Stores

by William Burns (JIRA)

William Burns created ISPN-6566: ----------------------------------- Summary: Segment information available for Cache Stores Key: ISPN-6566 URL: https://issues.jboss.org/browse/ISPN-6566 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: William Burns Assignee: William Burns Fix For: 9.0.0.Final Currently cache stores need to be iterated upon fully when doing bulk operations and also removal requires full iteration. It would be much more efficient if the cache store could store the entries by segment so they only have to read a portion of data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6540) Management console doesn't display cache containers correctly if there are two containers with the same name

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6540?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6540: ------------------------------------------- [~rmacor] I really appreciate your effort here. I will look into this remote sites today, solve it and then update the relevant PRs on both sides! > Management console doesn't display cache containers correctly if there are two containers with the same name > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6540 > URL: https://issues.jboss.org/browse/ISPN-6540 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: configs.zip, config_with_remoteSite.zip, Screenshot-containersWithSameName.png, Screenshot-detalPageForBothContainers.png > > > When we have two containers with the same name on different clusters some values are displayed correctly - #caches, name, clustering-info, but some are not - endpoints, sites. > Additionally, clicking on either of containers display the same information, even though containers are configured differently. > Please see the screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6564) CacheContainer screen not populated after cache configuration update

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6564?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6564: ------------------------------- Status: Open (was: New) > CacheContainer screen not populated after cache configuration update > -------------------------------------------------------------------- > > Key: ISPN-6564 > URL: https://issues.jboss.org/browse/ISPN-6564 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Update default cache configuration, confirm update and select either restart option. The resulting cache container screen is not populated due to the following error: > {code} > angular.js:12416 ReferenceError: cluster is not defined > at Scope.$scope.refresh (http://localhost:3000/cluster-view/cluster-view.controller.js:141:45) > at new <anonymous> (http://localhost:3000/cluster-view/cluster-view.controller.js:154:16) > at invoke (http://localhost:3000/built_components/angular/angular.js:4473:17) > at Object.instantiate (http://localhost:3000/built_components/angular/angular.js:4481:27) > at http://localhost:3000/built_components/angular/angular.js:9108:28 > at http://localhost:3000/built_components/angular-ui-router/release/angular-... > at invokeLinkFn (http://localhost:3000/built_components/angular/angular.js:8746:9) > at nodeLinkFn (http://localhost:3000/built_components/angular/angular.js:8246:11) > at compositeLinkFn (http://localhost:3000/built_components/angular/angular.js:7637:13) > at publicLinkFn (http://localhost:3000/built_components/angular/angular.js:7512:30) <div ui-view="" class="ng-scope"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6565) Remove command doesn't work in server

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6565: ------------------------------------- Summary: Remove command doesn't work in server Key: ISPN-6565 URL: https://issues.jboss.org/browse/ISPN-6565 Project: Infinispan Issue Type: Bug Components: CLI, Server Affects Versions: 9.0.0.Alpha1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.2.2.Final, 9.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6564) CacheContainer screen not populated after cache configuration update

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6564?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6564: ------------------------------- Description: Update default cache configuration, confirm update and select either restart option. The resulting cache container screen is not populated due to the following error: {code} angular.js:12416 ReferenceError: cluster is not defined at Scope.$scope.refresh (http://localhost:3000/cluster-view/cluster-view.controller.js:141:45) at new <anonymous> (http://localhost:3000/cluster-view/cluster-view.controller.js:154:16) at invoke (http://localhost:3000/built_components/angular/angular.js:4473:17) at Object.instantiate (http://localhost:3000/built_components/angular/angular.js:4481:27) at http://localhost:3000/built_components/angular/angular.js:9108:28 at http://localhost:3000/built_components/angular-ui-router/release/angular-... at invokeLinkFn (http://localhost:3000/built_components/angular/angular.js:8746:9) at nodeLinkFn (http://localhost:3000/built_components/angular/angular.js:8246:11) at compositeLinkFn (http://localhost:3000/built_components/angular/angular.js:7637:13) at publicLinkFn (http://localhost:3000/built_components/angular/angular.js:7512:30) <div ui-view="" class="ng-scope"> {code} > CacheContainer screen not populated after cache configuration update > -------------------------------------------------------------------- > > Key: ISPN-6564 > URL: https://issues.jboss.org/browse/ISPN-6564 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > Update default cache configuration, confirm update and select either restart option. The resulting cache container screen is not populated due to the following error: > {code} > angular.js:12416 ReferenceError: cluster is not defined > at Scope.$scope.refresh (http://localhost:3000/cluster-view/cluster-view.controller.js:141:45) > at new <anonymous> (http://localhost:3000/cluster-view/cluster-view.controller.js:154:16) > at invoke (http://localhost:3000/built_components/angular/angular.js:4473:17) > at Object.instantiate (http://localhost:3000/built_components/angular/angular.js:4481:27) > at http://localhost:3000/built_components/angular/angular.js:9108:28 > at http://localhost:3000/built_components/angular-ui-router/release/angular-... > at invokeLinkFn (http://localhost:3000/built_components/angular/angular.js:8746:9) > at nodeLinkFn (http://localhost:3000/built_components/angular/angular.js:8246:11) > at compositeLinkFn (http://localhost:3000/built_components/angular/angular.js:7637:13) > at publicLinkFn (http://localhost:3000/built_components/angular/angular.js:7512:30) <div ui-view="" class="ng-scope"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6564) CacheContainer screen not populated after cache configuration update

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-6564: ---------------------------------- Summary: CacheContainer screen not populated after cache configuration update Key: ISPN-6564 URL: https://issues.jboss.org/browse/ISPN-6564 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Alpha1 Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6555) Remove references to Deprecated fields 'queue-size' and 'queue-flush-interval'

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6555?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6555. -------------------------------- Resolution: Done > Remove references to Deprecated fields 'queue-size' and 'queue-flush-interval' > ------------------------------------------------------------------------------ > > Key: ISPN-6555 > URL: https://issues.jboss.org/browse/ISPN-6555 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > When loading "Cache containers" >> "clustered" >> "default(Distributed, Sync, 2 owners )" >> "Configuration" the General tab does not show Field names or their inputs. > This is caused because {code}$scope.metadata['queue-size']{code} and {code}$scope.metadata['queue-flush-interval']{code} are undefined in configurationSection.js when function $scope.cleanFieldMetadata is called. > I have checked the underlying DMR command, shown below, using the cli and this does not return any fields with those names. > {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=clustered:read-resource-description(recursive=true){code} > This is caused by the following ISPN changes: > https://github.com/infinispan/infinispan/commit/86477351795fac59750e2d574... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6555) Remove references to Deprecated fields 'queue-size' and 'queue-flush-interval'

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6555?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6555: ------------------------------- Fix Version/s: 9.0.0.Alpha2 > Remove references to Deprecated fields 'queue-size' and 'queue-flush-interval' > ------------------------------------------------------------------------------ > > Key: ISPN-6555 > URL: https://issues.jboss.org/browse/ISPN-6555 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha2 > > > When loading "Cache containers" >> "clustered" >> "default(Distributed, Sync, 2 owners )" >> "Configuration" the General tab does not show Field names or their inputs. > This is caused because {code}$scope.metadata['queue-size']{code} and {code}$scope.metadata['queue-flush-interval']{code} are undefined in configurationSection.js when function $scope.cleanFieldMetadata is called. > I have checked the underlying DMR command, shown below, using the cli and this does not return any fields with those names. > {code} /profile=clustered/subsystem=datagrid-infinispan/cache-container=clustered:read-resource-description(recursive=true){code} > This is caused by the following ISPN changes: > https://github.com/infinispan/infinispan/commit/86477351795fac59750e2d574... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6557) Obtain the Matcher eagerly in QueryEngine and avoid further costs to look it up

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6557?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6557: -------------------------------- Description: QueryEngine.getMatcher() is called many times and it always hits the component registry. The matcher could be retrieved once during construction and cached for later usage. (was: QueryEngine.getMatcher() is called many times and it always hits the component registry.) > Obtain the Matcher eagerly in QueryEngine and avoid further costs to look it up > ------------------------------------------------------------------------------- > > Key: ISPN-6557 > URL: https://issues.jboss.org/browse/ISPN-6557 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.0.0.Alpha2 > > > QueryEngine.getMatcher() is called many times and it always hits the component registry. The matcher could be retrieved once during construction and cached for later usage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6557) Obtain the Matcher eagerly in QueryEngine and avoid further costs to look it up

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6557?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6557: -------------------------------- Priority: Minor (was: Major) > Obtain the Matcher eagerly in QueryEngine and avoid further costs to look it up > ------------------------------------------------------------------------------- > > Key: ISPN-6557 > URL: https://issues.jboss.org/browse/ISPN-6557 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.0.0.Alpha2 > > > QueryEngine.getMatcher() is called many times and it always hits the component registry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016