May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6742) Console shows cache available even when cache is disabled

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-6742: --------------------------------- Summary: Console shows cache available even when cache is disabled Key: ISPN-6742 URL: https://issues.jboss.org/browse/ISPN-6742 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.2.2.Final Reporter: Jiří Holuša Assignee: Vladimir Blagojevic Page: go to cache detail and click "Actions" -> "Disable". After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6740) Client topologies not updated when cache topology loaded from persistent state

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6740?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6740: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4391 > Client topologies not updated when cache topology loaded from persistent state > ------------------------------------------------------------------------------ > > Key: ISPN-6740 > URL: https://issues.jboss.org/browse/ISPN-6740 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, State Transfer > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: > {code} > 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) > ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z > .... > 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) > Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, > pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[ > bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default > {code} > If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. > We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. > Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6740) Client topologies not updated when cache topology loaded from persistent state

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6740?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6740: ------------------------------- Status: Open (was: New) > Client topologies not updated when cache topology loaded from persistent state > ------------------------------------------------------------------------------ > > Key: ISPN-6740 > URL: https://issues.jboss.org/browse/ISPN-6740 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, State Transfer > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: > {code} > 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) > ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z > .... > 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) > Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, > pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[ > bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default > {code} > If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. > We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. > Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6740) Client topologies not updated when cache topology loaded from persistent state

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6740?page=com.atlassian.jira.plugin.... ] Work on ISPN-6740 started by Dan Berindei. ------------------------------------------ > Client topologies not updated when cache topology loaded from persistent state > ------------------------------------------------------------------------------ > > Key: ISPN-6740 > URL: https://issues.jboss.org/browse/ISPN-6740 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, State Transfer > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: > {code} > 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) > ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z > .... > 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) > Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, > pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[ > bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default > {code} > If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. > We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. > Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6716) Overlapping logging ids in serveral modules: object-filter, remote-query-server

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6716?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6716: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Overlapping logging ids in serveral modules: object-filter, remote-query-server > ------------------------------------------------------------------------------- > > Key: ISPN-6716 > URL: https://issues.jboss.org/browse/ISPN-6716 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.0.0.Alpha3, 9.0.0.Final, 8.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6741) Query named parameters must be single-valued, except in collection filters

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6741: ----------------------------------- Summary: Query named parameters must be single-valued, except in collection filters Key: ISPN-6741 URL: https://issues.jboss.org/browse/ISPN-6741 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Reporter: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6740) Client topologies not updated when cache topology loaded from persistent state

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-6740: -------------------------------------- Summary: Client topologies not updated when cache topology loaded from persistent state Key: ISPN-6740 URL: https://issues.jboss.org/browse/ISPN-6740 Project: Infinispan Issue Type: Bug Components: Remote Protocols, State Transfer Affects Versions: 8.2.2.Final, 9.0.0.Alpha2 Reporter: Galder Zamarreño Assignee: Dan Berindei Fix For: 9.0.0.Alpha3, 9.0.0.Final Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: {code} 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z .... 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default {code} If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6740) Client topologies not updated when cache topology loaded from persistent state

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6740?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6740: ----------------------------------- Description: Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: {code} 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z .... 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[ bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default {code} If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. was: Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: {code} 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z .... 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default {code} If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. > Client topologies not updated when cache topology loaded from persistent state > ------------------------------------------------------------------------------ > > Key: ISPN-6740 > URL: https://issues.jboss.org/browse/ISPN-6740 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, State Transfer > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > Infinispan Caches now support storing persistent views. When these are loaded, these might be loaded with topology ID 0: > {code} > 2016-05-31 10:20:04,254 INFO [org.infinispan.globalstate.impl.GlobalStateManagerImpl] (MSC service thread 1-3) > ISPN000389: Loaded global state, version=9.0.0-SNAPSHOT timestamp=2016-05-30T12:03:33.822Z > .... > 2016-05-31 10:20:07,867 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (MSC service thread 1-6) > Installing new cache topology CacheTopology{id=0, rebalanceId=0, currentCH=DefaultConsistentHash{ns=20, owners = (3)[node5: 7+5, node4: 7+7, node6: 6+8]}, > pendingCH=null, unionCH=null, actualMembers=[node5, node4, node6], persistentUUIDs=[ > bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf, bb76729d-2b30-4e54-8108-4ac1db9a04cf]} on cache default > {code} > If there's no further view changes, the topology ID will remain 0. When a Hot Rod client first connects, it sends its view topology as 0 so that it receives a newly installed topology, but if the topology is already 0 in the server, the server won't send the installed topology, even though it should be newer than having no topology. > We should start numbering topologies in server starting from 1 instead. That avoids this issue. This is easier than forcing clients to send -1 as initial topology because the topology ID is currently defined as VInt that can only 0 or positive number. > Also, some extra log messages indicating that the cache topology installed comes from persisted state would be handy for debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6739) tools.jar doesn't include META-INF services

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6739?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6739: ---------------------------------- Status: Open (was: New) > tools.jar doesn't include META-INF services > ------------------------------------------- > > Key: ISPN-6739 > URL: https://issues.jboss.org/browse/ISPN-6739 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 9.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha3 > > > The bundle plugin doesn't include generated meta-inf services files by default -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6739) tools.jar doesn't include META-INF services

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6739?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6739: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4390 > tools.jar doesn't include META-INF services > ------------------------------------------- > > Key: ISPN-6739 > URL: https://issues.jboss.org/browse/ISPN-6739 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 9.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha3 > > > The bundle plugin doesn't include generated meta-inf services files by default -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016