April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8689) Wildfly-modules should be created using wildfly feature packs

by Fabio Massimo Ercoli (JIRA)

[ https://issues.jboss.org/browse/ISPN-8689?page=com.atlassian.jira.plugin.... ] Fabio Massimo Ercoli commented on ISPN-8689: -------------------------------------------- Hi, I was wondering if maybe it's better to have 2 different feature packs: * one for embedded / library mode * one for remote only What do you think? > Wildfly-modules should be created using wildfly feature packs > ------------------------------------------------------------- > > Key: ISPN-8689 > URL: https://issues.jboss.org/browse/ISPN-8689 > Project: Infinispan > Issue Type: Enhancement > Components: WildFly modules > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Final > > > Currently we utilise an ant script to create the wildfly-module zips, instead we should utilise the `wildfly-feature-pack-build-maven-plugin` to generate them. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9003) Clustered maxIdle expiration

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9003: ------------------------------------- We already have a timer task, the expiration reaper :) Also state transfer entities are not refreshed from an iterator invocation (they only refresh on a get or write operation). In regards to divergent clocks, this is not an issue as long as we don't send timestampes across nodes (which we don't). Every node uses the provided offset of its own current time to detect expiration. Thus since writes should occur somewhat close to each other in absolute time the expiration of various nodes would be done with only a time differential of just about the latency time between primary and backup. So this could cause an entry to be resurrected if someone read it between this time, but tbh this seems more than okay to me. Lifespan works in a similar fashion, but it actually errs on the other side in that if it expired on any node it assumes all are expired (which is much less costly network wise). > Clustered maxIdle expiration > ---------------------------- > > Key: ISPN-9003 > URL: https://issues.jboss.org/browse/ISPN-9003 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8973) Administration console - changing eviction strategy results in error

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8973?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-8973: ------------------------------------------- [~wburns] and [~ryanemerson] I've traced this one to the update of the memory model. The NPE exception is https://gist.github.com/vblagoje/039096a67c525a241b33bc81e1dc094c However, I was unable to find the cause of it even with a debugger turned on. I've traced all javascript objects and DMR commands and they seemed fine. Creation of the memory node works ok. However, on an update, I get NPE. (see attachment). The NPE happens when the size is set to any value. In my tests I used 10L. But it fails on any long value. Any help is appreciated. > Administration console - changing eviction strategy results in error > -------------------------------------------------------------------- > > Key: ISPN-8973 > URL: https://issues.jboss.org/browse/ISPN-8973 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2018-04-03 at 2.42.46 PM.png > > > Steps to reproduce: > - start server in domain mode > - click on cache container -> cache -> configuration -> memory tab -> set memory > - e.g. (Type: binary, Eviction: count, Size: 10, strategy: FIFO) > - apply changes -> restart now > - change the strategy to LRU, click apply changes > That results in error popup: > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:":{"server-group":{"cluster":{"host":{"master":{"server-one":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}},"server-two":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}}}}}}}} > There are no error logs in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8973) Administration console - changing eviction strategy results in error

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8973?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8973: -------------------------------------- Attachment: Screen Shot 2018-04-03 at 2.42.46 PM.png > Administration console - changing eviction strategy results in error > -------------------------------------------------------------------- > > Key: ISPN-8973 > URL: https://issues.jboss.org/browse/ISPN-8973 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2018-04-03 at 2.42.46 PM.png > > > Steps to reproduce: > - start server in domain mode > - click on cache container -> cache -> configuration -> memory tab -> set memory > - e.g. (Type: binary, Eviction: count, Size: 10, strategy: FIFO) > - apply changes -> restart now > - change the strategy to LRU, click apply changes > That results in error popup: > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:":{"server-group":{"cluster":{"host":{"master":{"server-one":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}},"server-two":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}}}}}}}} > There are no error logs in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8973) Administration console - changing eviction strategy results in error

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8973?page=com.atlassian.jira.plugin.... ] Roman Macor commented on ISPN-8973: ----------------------------------- No, it could have been a long time ago - I found it when I was fixing a broken test which hasn't run for a while. > Administration console - changing eviction strategy results in error > -------------------------------------------------------------------- > > Key: ISPN-8973 > URL: https://issues.jboss.org/browse/ISPN-8973 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > - start server in domain mode > - click on cache container -> cache -> configuration -> memory tab -> set memory > - e.g. (Type: binary, Eviction: count, Size: 10, strategy: FIFO) > - apply changes -> restart now > - change the strategy to LRU, click apply changes > That results in error popup: > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:":{"server-group":{"cluster":{"host":{"master":{"server-one":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}},"server-two":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}}}}}}}} > There are no error logs in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9033) Web/CLI hangs if cache use cache store and has a lot of entries

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9033?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9033: ------------------------------- Component/s: Core > Web/CLI hangs if cache use cache store and has a lot of entries > --------------------------------------------------------------- > > Key: ISPN-9033 > URL: https://issues.jboss.org/browse/ISPN-9033 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Sergey Chernolyas > > My cache configuration has RocksDB's cache. Cache has a more then 1 000 000 entries. > And it do usage of Web interfce and CLI impossible. > As I have investigated, problem can be in class org.infinispan.commands.read.SizeCommand. > {code:java} > public Integer perform(InvocationContext ctx) throws Throwable { > long size = cache.keySet().stream().count(); > if (size > Integer.MAX_VALUE) { > return Integer.MAX_VALUE; > } else { > return (int) size; > } > } > {code} > I think, the code must ask CacheStore for sizing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9033) Web/CLI hangs if cache use cache store and has a lot of entries

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9033?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9033: ------------------------------- Priority: Major (was: Blocker) > Web/CLI hangs if cache use cache store and has a lot of entries > --------------------------------------------------------------- > > Key: ISPN-9033 > URL: https://issues.jboss.org/browse/ISPN-9033 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.1.Final > Reporter: Sergey Chernolyas > > My cache configuration has RocksDB's cache. Cache has a more then 1 000 000 entries. > And it do usage of Web interfce and CLI impossible. > As I have investigated, problem can be in class org.infinispan.commands.read.SizeCommand. > {code:java} > public Integer perform(InvocationContext ctx) throws Throwable { > long size = cache.keySet().stream().count(); > if (size > Integer.MAX_VALUE) { > return Integer.MAX_VALUE; > } else { > return (int) size; > } > } > {code} > I think, the code must ask CacheStore for sizing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9033) Web/CLI hangs if cache use cache store and has a lot of entries

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9033?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9033: ------------------------------- Issue Type: Bug (was: Feature Request) > Web/CLI hangs if cache use cache store and has a lot of entries > --------------------------------------------------------------- > > Key: ISPN-9033 > URL: https://issues.jboss.org/browse/ISPN-9033 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.1.Final > Reporter: Sergey Chernolyas > Priority: Blocker > > My cache configuration has RocksDB's cache. Cache has a more then 1 000 000 entries. > And it do usage of Web interfce and CLI impossible. > As I have investigated, problem can be in class org.infinispan.commands.read.SizeCommand. > {code:java} > public Integer perform(InvocationContext ctx) throws Throwable { > long size = cache.keySet().stream().count(); > if (size > Integer.MAX_VALUE) { > return Integer.MAX_VALUE; > } else { > return (int) size; > } > } > {code} > I think, the code must ask CacheStore for sizing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8973) Administration console - changing eviction strategy results in error

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8973?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-8973: ------------------------------------------- Confirmed [~rmacor]. Any chance you noticed when this regression started to show up? > Administration console - changing eviction strategy results in error > -------------------------------------------------------------------- > > Key: ISPN-8973 > URL: https://issues.jboss.org/browse/ISPN-8973 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > - start server in domain mode > - click on cache container -> cache -> configuration -> memory tab -> set memory > - e.g. (Type: binary, Eviction: count, Size: 10, strategy: FIFO) > - apply changes -> restart now > - change the strategy to LRU, click apply changes > That results in error popup: > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:":{"server-group":{"cluster":{"host":{"master":{"server-one":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}},"server-two":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}}}}}}}} > There are no error logs in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8973) Administration console - changing eviction strategy results in error

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8973?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8973: -------------------------------------- Status: Open (was: New) > Administration console - changing eviction strategy results in error > -------------------------------------------------------------------- > > Key: ISPN-8973 > URL: https://issues.jboss.org/browse/ISPN-8973 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > - start server in domain mode > - click on cache container -> cache -> configuration -> memory tab -> set memory > - e.g. (Type: binary, Eviction: count, Size: 10, strategy: FIFO) > - apply changes -> restart now > - change the strategy to LRU, click apply changes > That results in error popup: > {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:":{"server-group":{"cluster":{"host":{"master":{"server-one":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}},"server-two":{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-3":"WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}}}}}}}} > There are no error logs in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018