May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6583) Can't update cache configuration unknown field 'is-create-mode'

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-6583: ---------------------------------- Summary: Can't update cache configuration unknown field 'is-create-mode' Key: ISPN-6583 URL: https://issues.jboss.org/browse/ISPN-6583 Project: Infinispan Issue Type: Bug Components: Console Reporter: Ryan Emerson Assignee: Ryan Emerson Introduced by https://github.com/infinispan/infinispan-management-console/pull/86 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6104) Cache.Purge issues

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6104?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6104: ---------------------------------- Assignee: Tristan Tarrant (was: Pedro Zapata) > Cache.Purge issues > ------------------ > > Key: ISPN-6104 > URL: https://issues.jboss.org/browse/ISPN-6104 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Optional > > Currently, there are the following issues with the "Purge cache data" button: > 1) The Purge operation only copies entries to the cache store, it does not remove the from the cache itself. So the cache remains full. Checked with cache.withFlags(Flag.SKIP_CACHE_LOAD).get() after I performed the Purge operation and still got the entries. The JMX stats also display entries in the cache. > 2) The button is available even though the cache is attached to the remote endpoint and hence available to clients. It should only be available after the cache is detached from the endpoint. > 3) The confirmation dialog for the operation always says "Purging cache xyCache will passivate all its cache entries." even though there's no cache store defined for the cache. This might lead users to expectations that their data will be stored somewhere. But if there's no cache store, the data will be lost. In this case, it would be better to show a warning that their data will be lost after performing the operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6104) Cache.Purge issues

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6104?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6104: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > Cache.Purge issues > ------------------ > > Key: ISPN-6104 > URL: https://issues.jboss.org/browse/ISPN-6104 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Pedro Zapata > Priority: Optional > > Currently, there are the following issues with the "Purge cache data" button: > 1) The Purge operation only copies entries to the cache store, it does not remove the from the cache itself. So the cache remains full. Checked with cache.withFlags(Flag.SKIP_CACHE_LOAD).get() after I performed the Purge operation and still got the entries. The JMX stats also display entries in the cache. > 2) The button is available even though the cache is attached to the remote endpoint and hence available to clients. It should only be available after the cache is detached from the endpoint. > 3) The confirmation dialog for the operation always says "Purging cache xyCache will passivate all its cache entries." even though there's no cache store defined for the cache. This might lead users to expectations that their data will be stored somewhere. But if there's no cache store, the data will be lost. In this case, it would be better to show a warning that their data will be lost after performing the operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6581) Remote events generated by remote typed exec can result in ClassCastException

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6581?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6581: ----------------------------------- Description: If the script modifies the cache passing anything other than byte[], ClassCastException instances will be generated when sending events related to cache operations resulting from remote execution. This affects only data typed scripts. was: If the script modifies the cache passing anything other than byte[], ClassCastException instances will be generated when sending events related to cache operations resulting from remote execution. This affects both data typed and untyped scripts. Summary: Remote events generated by remote typed exec can result in ClassCastException (was: Remote events generated by remote execution can result in ClassCastException) > Remote events generated by remote typed exec can result in ClassCastException > ----------------------------------------------------------------------------- > > Key: ISPN-6581 > URL: https://issues.jboss.org/browse/ISPN-6581 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Tasks > Affects Versions: 8.2.0.Final, 9.0.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > If the script modifies the cache passing anything other than byte[], ClassCastException instances will be generated when sending events related to cache operations resulting from remote execution. > This affects only data typed scripts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6500) can't edit indexing properties in console

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6500?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6500: ------------------------------- Status: Open (was: New) > can't edit indexing properties in console > ----------------------------------------- > > Key: ISPN-6500 > URL: https://issues.jboss.org/browse/ISPN-6500 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Ryan Emerson > > in cache configuration -> indexing -> indexing properties if I edit the filed to e.g. [default.directory_provider ram] -> click update. then If I check if indexing properties was changed, the field is blank. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6500) can't edit indexing properties in console

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6500?page=com.atlassian.jira.plugin.... ] Work on ISPN-6500 started by Ryan Emerson. ------------------------------------------ > can't edit indexing properties in console > ----------------------------------------- > > Key: ISPN-6500 > URL: https://issues.jboss.org/browse/ISPN-6500 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Ryan Emerson > > in cache configuration -> indexing -> indexing properties if I edit the filed to e.g. [default.directory_provider ram] -> click update. then If I check if indexing properties was changed, the field is blank. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6502) can't edit cache type in console

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6502?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-6502. -------------------------------- Fix Version/s: 9.0.0.Alpha2 Resolution: Done > can't edit cache type in console > -------------------------------- > > Key: ISPN-6502 > URL: https://issues.jboss.org/browse/ISPN-6502 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Ryan Emerson > Fix For: 9.0.0.Alpha2 > > > cache configuration -> general -> type > after change the cache type an alert window with error message is shown > domain-failure-description > WFLYCTL0216: Management resource '[ ("profile" => "clustered"), ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered"), ("configurations" => "CONFIGURATIONS"), ("distributed-cache-configuration" => "replicatedCacheForStatisticsTesting") ]' not found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5968) Cache statistics are not shown for local caches in mgmt console

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-5968?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-5968. -------------------------------- Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Cache statistics are not shown for local caches in mgmt console > --------------------------------------------------------------- > > Key: ISPN-5968 > URL: https://issues.jboss.org/browse/ISPN-5968 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > Page: Caches -> select cache container -> select some local cache > When you look at the statistics, no numbers are shown, even zeros. When you put some entries to the cache, nothing changes. Note that this work fine when the cache is not local, e.g. distributed, replicated, etc... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6114) Management console - node view - performance and caching activities are not calculated properly

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-6114?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-6114: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > Management console - node view - performance and caching activities are not calculated properly > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6114 > URL: https://issues.jboss.org/browse/ISPN-6114 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Pedro Zapata > > Clusters tab -> click on cluster -> click on node > After doing operations on cache that is deployed on node the statistics (e.g. #PUTS) still display 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6559) Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5"

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6559?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reopened ISPN-6559: ------------------------------------- Reopening until patch applied on master as well > Provide module for Infinispan Directory that satisfies the slot "for-hibernatesearch-5.5" > ----------------------------------------------------------------------------------------- > > Key: ISPN-6559 > URL: https://issues.jboss.org/browse/ISPN-6559 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 8.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.2.Final > > > Wildfly 10.0.0 internal hibernate search engine has an optional dependency to > {code:xml} >  > <module name="org.infinispan.hibernate-search.directory-provider" slot="for-hibernatesearch-5.5" services="import" optional="true"/> > {code} > But as described in ISPN-6537 this dependency is not correctly satisfied by the modules zip, forcing users who depends on hibernate from wildfly to use the ispn-8.1 slot and thus another version of hibernate search -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2016