May 2016 - infinispan-issues - Jboss List Archives

[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 updated ISPN-6559: ------------------------------------ Fix Version/s: 9.0.0.Alpha2 9.0.0.Final > 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: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.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

[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 updated ISPN-6559: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4280, https://github.com/infinispan/infinispan/pull/4298 (was: https://github.com/infinispan/infinispan/pull/4280) > 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: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.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

[JBoss JIRA] (ISPN-6580) Hotrod performance regressions after ISPN-5342 ISPN-6545

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6580?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-6580: ------------------------------------- Yeah that was my fault thinking that jboss logging level would inherit like all the other major providers :P I had since updated the default standalone.xml to set it to INFO explicitly. I am looking into the issue though. > Hotrod performance regressions after ISPN-5342 ISPN-6545 > -------------------------------------------------------- > > Key: ISPN-6580 > URL: https://issues.jboss.org/browse/ISPN-6580 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Server > Reporter: Jakub Markos > Assignee: William Burns > Attachments: jfr_recordings.zip, pom.xml, Reproducer.java > > > There were 2 recent regressions in hotrod performance, one between commits dd5501c5e and 628819461 and the second one between 628819461 and db0890270. I didn't look for the exact commits, so the name of the issue might not be 100% exact... > It is easily reproducable locally with a single server instance, reproducer attached. > The numbers on my machine: > ||Build commit||Puts time||Gets time|| > |dd5501c5e|21|74| > |628819461|26|102| > |db0890270|48|224| > The JFR recordings (attached, captured is only the part of the test with gets) for db0890270 show a lot of time is spent in HotRodDecoder#resetNow(), and also the allocation rate goes from 100MB/s for dd5501c5e to over 1GB/s for db0890270. There are no glaring differences between dd5501c5e and 628819461. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-5972: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Pedro Zapata > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-5972: ------------------------------- Status: Open (was: New) > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Pedro Zapata > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Zapata commented on ISPN-5972: ------------------------------------ The console is displaying clusterwide-number-of-entries instead of number-of-entries. That's probably the problem. [domain@localhost:9990 cache-container=clustered] cd replicated-cache=myrepl [domain@localhost:9990 replicated-cache=myrepl] ls ... clusterwide-misses=1000 clusterwide-number-of-entries=2000 number-of-entries=1000 clusterwide-stores=1000 ... > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5972) Number of entries not working correctly in cache statistics in mgmt console

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5972?page=com.atlassian.jira.plugin.... ] Pedro Zapata commented on ISPN-5972: ------------------------------------ I have tested with ER4, putting 1000 items from a remote HR client into a cache. The values displayed are: With DIST -> Entries = 1000 (correct) With REPL -> Entries = 2000 (incorrect) > Number of entries not working correctly in cache statistics in mgmt console > --------------------------------------------------------------------------- > > Key: ISPN-5972 > URL: https://issues.jboss.org/browse/ISPN-5972 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: replicated cache, 2 nodes in the domain > In the "Cache content" tab, there is a field "# Entries" which should probably show number of entries in the cache. When I put 100 entries in the cache, this field shows 200. Given that it's replicated cache, I think what's happening is that it shows numberOfNodes*numberOfEntries, because when I try to put 100 entries with 3 nodes in the domain, the "# Entries" shows 300. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6582) JDBC isUpsertSupported() does not respect Semantic Versioning

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-6582: ---------------------------------- Summary: JDBC isUpsertSupported() does not respect Semantic Versioning Key: ISPN-6582 URL: https://issues.jboss.org/browse/ISPN-6582 Project: Infinispan Issue Type: Bug Reporter: Ryan Emerson Assignee: Ryan Emerson -- 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 execution can result in ClassCastException

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-6581: -------------------------------------- Summary: Remote events generated by remote execution 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: 9.0.0.Alpha1, 8.2.0.Final 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 both data typed and untyped scripts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 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: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4271/, https://github.com/infinispan/infinispan/pull/4297 (was: 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 > 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)

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