April 2016 - infinispan-issues - Jboss List Archives

[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 updated ISPN-6540: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/84/ > 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, 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, 8 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 edited comment on ISPN-6540 at 4/26/16 8:24 PM: -------------------------------------------------------------------- [~rmacor] Great catch. I had to revamp quite a bit in order to fix this one. Would you please try it out on infinispan master and make sure that are no regressions. I tried it myself but this one needs a lot of testing. Try it first on regular default setup and then on configuration setup you attached. It would help if you can test with you automated tests as well. Let's keep in touch! was (Author: vblagojevic): [~rmacor] Great catch. I had to revamp quite a bit in order to fix this one. Would you please try it out on infinispan master and make sure that are no regressions. I tried it myself but this one needs a quite a bit of testing. Try it first on regular default setup and then on configuration setup you sent. It would help if you can test with you automated tests as well. Let's keep in touch! > 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, 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, 8 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: ------------------------------------------- Note that endpoints although duplicate - are correct. That's the data we get from DMR. I'll check with [~NadirX] > 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, 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, 8 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] Great catch. I had to revamp quite a bit in order to fix this one. Would you please try it out on infinispan master and make sure that are no regressions. I tried it myself but this one needs a quite a bit of testing. Try it first on regular default setup and then on configuration setup you sent. It would help if you can test with you automated tests as well. Let's keep in touch! > 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, 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6550) Remote iterator does not work in compatibility mode

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6550?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-6550: ----------------------------------- Assignee: Gustavo Fernandes > Remote iterator does not work in compatibility mode > --------------------------------------------------- > > Key: ISPN-6550 > URL: https://issues.jboss.org/browse/ISPN-6550 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > There are two issues when trying to iterate caches configured with compatibility: > 1) Since the client-side key tracker calculates segments based on byte[] keys, and the routing on the server is done via Object, there's a mismatch between segments calculated in the server and the client casing NPEs that prevent the data from the socket to be consumed correctly, resulting sometimes in: > {code} > org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0 > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:313) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:115) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.IterationEndOperation.execute(IterationEndOperation.java:34) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.close(RemoteCloseableIterator.java:64) > {code} > 2) When the cache configuration has a different name than the cache, CCE errors are thrown: > {code} > org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.ClassCastException: java.lang.Integer cannot be cast to [B > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6537) Support persistence of Hibernate Search/Lucene indexes

by John Schneider (JIRA)

[ https://issues.jboss.org/browse/ISPN-6537?page=com.atlassian.jira.plugin.... ] John Schneider commented on ISPN-6537: -------------------------------------- I was trying to use the Infinispan 8.1.0.Final and Hibernate Search 5.5 modules included with Wildfly 10.0 along separately downloaded infinispan-directory-provider and lucene-directory modules. It appears there's some incompatibility with the stock Wildfly modules. After installing the Infinispan 8.1.3 embedded modules and switching my app to use the ispn-8.1 slot and Hibernate Search slot 5.5 I am able to use the Lucene directory functionality without any issues. It would be really nice if I could just use the modules that are part of Wildfly, but I suppose this issue can be closed. > Support persistence of Hibernate Search/Lucene indexes > ------------------------------------------------------ > > Key: ISPN-6537 > URL: https://issues.jboss.org/browse/ISPN-6537 > Project: Infinispan > Issue Type: Feature Request > Components: Lucene Directory > Affects Versions: 8.1.0.Final > Environment: Wildfly 10.0.Final with infinispan-directory-provider and lucene-directory 8.1.0 final deployed as modules. > Reporter: John Schneider > > I'm able to use Infinispan for my HIbernate Search/Lucene indexes without any issues on Wildfly 10.0.Final with infinispan-directory-provider and lucene-directory 8.1.0 final deployed as modules. However, I need to persist the indexes to disk and when I add a file-store directive to my configuration, I get a NotSerializableException for org.infinispan.lucene.FileListCacheKey. I haven't gotten past this exception, so I don't know if this is as simple as implementing Serializable on FileListCacheKey or not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6120?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6120: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/83 > Management console - there should be a warning about possible data loss when stopping the cluster > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6120 > URL: https://issues.jboss.org/browse/ISPN-6120 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Clusters tab -> cluster -> actions -> stop > When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6120?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6120: -------------------------------------- Status: Open (was: New) > Management console - there should be a warning about possible data loss when stopping the cluster > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6120 > URL: https://issues.jboss.org/browse/ISPN-6120 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Clusters tab -> cluster -> actions -> stop > When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6550) Remote iterator does not work in compatibility mode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6550?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6550: ------------------------------------ Status: Open (was: New) > Remote iterator does not work in compatibility mode > --------------------------------------------------- > > Key: ISPN-6550 > URL: https://issues.jboss.org/browse/ISPN-6550 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Gustavo Fernandes > > There are two issues when trying to iterate caches configured with compatibility: > 1) Since the client-side key tracker calculates segments based on byte[] keys, and the routing on the server is done via Object, there's a mismatch between segments calculated in the server and the client casing NPEs that prevent the data from the socket to be consumed correctly, resulting sometimes in: > {code} > org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0 > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:313) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:115) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.IterationEndOperation.execute(IterationEndOperation.java:34) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.close(RemoteCloseableIterator.java:64) > {code} > 2) When the cache configuration has a different name than the cache, CCE errors are thrown: > {code} > org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.ClassCastException: java.lang.Integer cannot be cast to [B > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6550) Remote iterator does not work in compatibility mode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6550?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6550: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4271/ > Remote iterator does not work in compatibility mode > --------------------------------------------------- > > Key: ISPN-6550 > URL: https://issues.jboss.org/browse/ISPN-6550 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Gustavo Fernandes > > There are two issues when trying to iterate caches configured with compatibility: > 1) Since the client-side key tracker calculates segments based on byte[] keys, and the routing on the server is done via Object, there's a mismatch between segments calculated in the server and the client casing NPEs that prevent the data from the socket to be consumed correctly, resulting sometimes in: > {code} > org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0 > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:313) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:115) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.IterationEndOperation.execute(IterationEndOperation.java:34) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.close(RemoteCloseableIterator.java:64) > {code} > 2) When the cache configuration has a different name than the cache, CCE errors are thrown: > {code} > org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.ClassCastException: java.lang.Integer cannot be cast to [B > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 April 2016