January 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8558) Administration console - some events are not displayed in the console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8558?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-8558: ------------------------------------------- [~rmacor] These should be absolutely the same except that we fetch only ten events on the containers page, just as the preview, while on the actual status event page we fetch many more events. Depending on the menu drop down control that selects the number of events to fetch we fetch at least 100 events. Is that what you are talking about here? > Administration console - some events are not displayed in the console > --------------------------------------------------------------------- > > Key: ISPN-8558 > URL: https://issues.jboss.org/browse/ISPN-8558 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.2.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Some events are not displayed in the console. > e.g. > I see events in the server log, but not in the status event tab in the console: > 10 INFO [org.infinispan.CLUSTER] (transport-thread--p4-t24) [Context=___query_known_classes][Context=master:server-one]ISPN100003: Node master:server-one finished rebalance phase with topology id 12 > [Server:server-one] 11:06:08,011 INFO [org.infinispan.CLUSTER] (remote-thread--p2-t24) [Context=___query_known_classes][Context=master:server-two]ISPN100003: Node master:server-two finished rebalance phase with topology id 12 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7705) Administration console - greyed out cluster action can still be selected

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7705?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7705: -------------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/204, https://github.com/infinispan/infinispan-management-console/pull/227 (was: https://github.com/infinispan/infinispan-management-console/pull/204) > Administration console - greyed out cluster action can still be selected > ------------------------------------------------------------------------ > > Key: ISPN-7705 > URL: https://issues.jboss.org/browse/ISPN-7705 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final, 9.1.0.Final > > > When the cluster is in the running state, start, reload and restart actions are greyed out, but they can still be clicked and the selected action is performed. > This is not the case for the node operations. > Also, shouldn't restart action be available when server/node are in running state? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7705) Administration console - greyed out cluster action can still be selected

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7705?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7705: ------------------------------------------- Ok, no problem [~rmacor] so we should basically have these two buttons enabled all the time? > Administration console - greyed out cluster action can still be selected > ------------------------------------------------------------------------ > > Key: ISPN-7705 > URL: https://issues.jboss.org/browse/ISPN-7705 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Final > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.1.Final, 9.1.0.Final > > > When the cluster is in the running state, start, reload and restart actions are greyed out, but they can still be clicked and the selected action is performed. > This is not the case for the node operations. > Also, shouldn't restart action be available when server/node are in running state? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8651) Use functional commands for JCache operations

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8651?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8651: ------------------------------ Description: Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. -Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property.- JSR107 spec says that implementation may require the EntryProcessor to be serializable or marshallable in some manner. was: Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property. > Use functional commands for JCache operations > --------------------------------------------- > > Key: ISPN-8651 > URL: https://issues.jboss.org/browse/ISPN-8651 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > > Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. > -Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property.- > JSR107 spec says that implementation may require the EntryProcessor to be serializable or marshallable in some manner. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3267) Support all LevelDB options

by Takayoshi Kimura (JIRA)

[ https://issues.jboss.org/browse/ISPN-3267?page=com.atlassian.jira.plugin.... ] Takayoshi Kimura closed ISPN-3267. ---------------------------------- Resolution: Out of Date > Support all LevelDB options > --------------------------- > > Key: ISPN-3267 > URL: https://issues.jboss.org/browse/ISPN-3267 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 5.3.0.CR2 > Reporter: Takayoshi Kimura > Assignee: Takayoshi Kimura > > The current LevelDB cache store lacks some LevelDB options. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7932) JCache EntryProcesor not working for replicated cache

by Miljenko Brkic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7932?page=com.atlassian.jira.plugin.... ] Miljenko Brkic commented on ISPN-7932: -------------------------------------- [~rvansa] Hi, have you run it with "mvn spring-boot:run" (please check "Steps to Reproduce")? > JCache EntryProcesor not working for replicated cache > ----------------------------------------------------- > > Key: ISPN-7932 > URL: https://issues.jboss.org/browse/ISPN-7932 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 9.0.1.Final > Environment: Ubuntu Linux 4.4.0-79-generic x86_64 > java version "1.8.0_131" > Java(TM) SE Runtime Environment (build 1.8.0_131-b11) > Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) > Reporter: Miljenko Brkic > Assignee: Dan Berindei > Attachments: jcache.tar.gz > > > Cached value updated via EntryProcessor is not updated in replicated cache. > Please find attached test application to reproduce the problem. Two instances of application increment cached value, but for one instance new value is not put in the cache (see steps to reproduce). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8641) Upgrade to Wildfly 11

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8641?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8641: ------------------------------- Status: Open (was: New) > Upgrade to Wildfly 11 > --------------------- > > Key: ISPN-8641 > URL: https://issues.jboss.org/browse/ISPN-8641 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 9.2.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8641) Upgrade to Wildfly 11

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8641?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8641: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5656 > Upgrade to Wildfly 11 > --------------------- > > Key: ISPN-8641 > URL: https://issues.jboss.org/browse/ISPN-8641 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 9.2.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8652) Embedded JCache listener does not correctly return the previous value

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-8652: -------------------------------------- Summary: Embedded JCache listener does not correctly return the previous value Key: ISPN-8652 URL: https://issues.jboss.org/browse/ISPN-8652 Project: Infinispan Issue Type: Bug Components: JCache Affects Versions: 9.1.4.Final, 9.2.0.Beta2 Reporter: Galder Zamarreño See discussion [here|https://github.com/infinispan/infinispan/pull/5624#discussion_r15941...]. The cache entry modified embedded event does not easily expose the previous value. To get the previous value, you need to listen for isPre=true event and cache the value. This is not user friendly. The cache entry modified embedded event should probably expose a method to retrieve previous value regardless of whether isPre is true or false. The JCache TCK currently only verifies that the previous value is non null, so we can just the current value and the TCK passes, but this is not correct. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8651) Use functional commands for JCache operations

by Radim Vansa (JIRA)

Radim Vansa created ISPN-8651: --------------------------------- Summary: Use functional commands for JCache operations Key: ISPN-8651 URL: https://issues.jboss.org/browse/ISPN-8651 Project: Infinispan Issue Type: Enhancement Reporter: Radim Vansa Assignee: Radim Vansa Some JCache operations (especially the {{invoke}}) cannot be executed using single command. We should run those using functional commands if possible. Regarding the {{invoke}} we have to find out if the {{EntryProcessor}} is marshallable. If it is we will assume that it does not have any side-effect and can be invoked on remote node; we should let the user opt-out of this behaviour through a system property. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2018