April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11636) Remove node suspected error code from Hot Rod protocol

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11636?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez reassigned ISPN-11636: --------------------------------------------- Assignee: Dan Berindei > Remove node suspected error code from Hot Rod protocol > ------------------------------------------------------ > > Key: ISPN-11636 > URL: https://issues.redhat.com/browse/ISPN-11636 > Project: Infinispan > Issue Type: Task > Components: Hot Rod > Affects Versions: 11.0.0.Dev04 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > Hot Rod 2.0 introduced error code {{0x87}} for the client to retry when another node has been suspected. However, the server is already handling the retry itself since ISPN-3366/ISPN-4546, so the client should never receive error code {{0x87}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11643) REST connector misinterprets % in query path elements

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11643?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11643: ------------------------------------- Status: Open (was: New) > REST connector misinterprets % in query path elements > ----------------------------------------------------- > > Key: ISPN-11643 > URL: https://issues.redhat.com/browse/ISPN-11643 > Project: Infinispan > Issue Type: Bug > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The REST resource manager performs a QueryStringDecoder.decodeComponent on path elements that have already bee decoded by Netty. This causes a path like `a%25bc` to be converted to `a%bc` but then converted again to `a�` -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4847) Improve indexing performance

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-4847?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez closed ISPN-4847. ---------------------------------------- Resolution: Out of Date > Improve indexing performance > ---------------------------- > > Key: ISPN-4847 > URL: https://issues.redhat.com/browse/ISPN-4847 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Lucene Directory > Affects Versions: 7.0.0.CR1 > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Critical > > This JIRA is focused on optimizing performance of use case where the application uses short or none transactions - therefore, no batching can be applied - and then performs the query and expects that the result will be consistent (please, specify in documentation if any lag after cache.put() or tx.commit() is required and if the application can detect that the update has been applied). > We are well aware (see BZ) that indexing can be implemented with very low overhead, but the throughput is thousands of times lower [1] (configuration in [2]) with distributed mode storing index in replicated cache, and about 4x slowdown when comparing replicated cache without indexing and indexing to NRT FS/RAM. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4847) Improve indexing performance

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-4847?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez reassigned ISPN-4847: -------------------------------------------- Assignee: Gustavo Fernandes (was: Sanne GRINOVERO) > Improve indexing performance > ---------------------------- > > Key: ISPN-4847 > URL: https://issues.redhat.com/browse/ISPN-4847 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Lucene Directory > Affects Versions: 7.0.0.CR1 > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Critical > > This JIRA is focused on optimizing performance of use case where the application uses short or none transactions - therefore, no batching can be applied - and then performs the query and expects that the result will be consistent (please, specify in documentation if any lag after cache.put() or tx.commit() is required and if the application can detect that the update has been applied). > We are well aware (see BZ) that indexing can be implemented with very low overhead, but the throughput is thousands of times lower [1] (configuration in [2]) with distributed mode storing index in replicated cache, and about 4x slowdown when comparing replicated cache without indexing and indexing to NRT FS/RAM. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-index... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7268) Refactor Healthcheck API to use new REST management interface

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-7268?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez closed ISPN-7268. ---------------------------------------- Resolution: Out of Date > Refactor Healthcheck API to use new REST management interface > ------------------------------------------------------------- > > Key: ISPN-7268 > URL: https://issues.redhat.com/browse/ISPN-7268 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Sebastian Laskawiec > Assignee: Tristan Tarrant > Priority: Critical > > Refactor Healthcheck API to look similar to this: https://github.com/wildfly/wildfly-core/pull/1990/files > Additionally use new Management API: https://issues.jboss.org/browse/WFCORE-1742 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7497) While migrating to resteasy-jaxrs-2.1.0.GA.jar to resteasy-jaxrs-3.0.12-Final. jar by using jetty 6.1.11 getting exception like : org.jboss.resteasy.plugins.providers.jaxb.JAXBMarshalException: A valid XmlRegistry could not be located

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-7497?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez closed ISPN-7497. ---------------------------------------- Resolution: Out of Date > While migrating to resteasy-jaxrs-2.1.0.GA.jar to resteasy-jaxrs-3.0.12-Final. jar by using jetty 6.1.11 getting exception like : org.jboss.resteasy.plugins.providers.jaxb.JAXBMarshalException: A valid XmlRegistry could not be located > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-7497 > URL: https://issues.redhat.com/browse/ISPN-7497 > Project: Infinispan > Issue Type: Enhancement > Reporter: Mahendra B > Priority: Critical > > We are migrating resteasy jaxrs jars from 2.1.0 GA to 3.0.12.-Final. when we are trying to run the application, we are getting " org.jboss.resteasy.plugins.providers.jaxb.JAXBMarshalException: A valid XmlRegistry could not be located". > We are Jetty 6.1.11. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9380) NoClassDefFoundError : Could not initialize class org.jgroups.conf.XmlConfigurator

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9380?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9380: ----------------------------------------- Issue Type: Bug (was: Feature Request) > NoClassDefFoundError : Could not initialize class org.jgroups.conf.XmlConfigurator > ---------------------------------------------------------------------------------- > > Key: ISPN-9380 > URL: https://issues.redhat.com/browse/ISPN-9380 > Project: Infinispan > Issue Type: Bug > Components: Clustered Locks > Affects Versions: 9.3.0.Final > Environment: GITLAB CI > Reporter: Youness Younssi > Priority: Critical > > hello everybody, > can someone help me to fix this probleme please. > I want to use infinispan in my project with spring boot, it works correclty in local . > but in gitlab ci , the instanciantion of EmbeddedCacheManager doesnt work , > this line this.manager = new DefaultCacheManager(ispnCfgFile); genere me this error > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type JGroupsTransport > at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:83) > at org.infinispan.commons.util.SecurityActions.doPrivileged(SecurityActions.java:71) > at org.infinispan.commons.util.SecurityActions.invokeAccessibly(SecurityActions.java:76) > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:185) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:968) > at org.infinispan.factories.AbstractComponentRegistry.lambda$invokePrioritizedMethods$6(AbstractComponentRegistry.java:703) > at org.infinispan.factories.SecurityActions.lambda$run$1(SecurityActions.java:72) > at org.infinispan.security.Security.doPrivileged(Security.java:44) > at org.infinispan.factories.SecurityActions.run(SecurityActions.java:71) > at org.infinispan.factories.AbstractComponentRegistry.invokePrioritizedMethods(AbstractComponentRegistry.java:696) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:689) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:607) > at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:250) > ... 57 common frames omitted > Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jgroups.conf.XmlConfigurator > the content of the file ispnCfgFile is : > <?xml version="1.0" encoding="UTF-8"?> > <infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:infinispan:config:9.3 http://infinispan.org/schemas/infinispan-config-9.3.xsd" > xmlns="urn:infinispan:config:9.3"> > <jgroups> > <stack-file name="tcpStack" path="${infinispan.configClusterFilePath:ispn/moose-jgroups-tcp.xml}"/> > </jgroups> > <cache-container default-cache="moose-data" statistics="true"> > <transport stack="tcpStack" cluster="mooseCluster"/> > <jmx/> > <replicated-cache name="moose-data" mode="SYNC" remote-timeout="1000"> > <state-transfer timeout="1000"/> > <locking acquire-timeout="1000"/> > <transaction mode="NON_XA" locking="PESSIMISTIC"/> > </replicated-cache> > </cache-container> > </infinispan> > the dependency that i added in my pom file for to integrate infinispan is : > dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-clustered-lock</artifactId> > <version>9.3.0.Final</version> > </dependency> > thank you very much in advance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11181) Upgrade JS Client to Infinispan 10

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11181?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez closed ISPN-11181. ----------------------------------------- Resolution: Done > Upgrade JS Client to Infinispan 10 > ---------------------------------- > > Key: ISPN-11181 > URL: https://issues.redhat.com/browse/ISPN-11181 > Project: Infinispan > Issue Type: Feature Request > Components: Integration > Affects Versions: 9.4.17.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Labels: js > > upgrade the JS client to work with Infinispan 10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11223) Support tcp_keepalive_time, tcp_keepalive_intvl, tcp_keepalive_probes for our (HotRod|Rest) clients

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11223?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11223: ------------------------------------------ Priority: Major (was: Critical) > Support tcp_keepalive_time, tcp_keepalive_intvl, tcp_keepalive_probes for our (HotRod|Rest) clients > --------------------------------------------------------------------------------------------------- > > Key: ISPN-11223 > URL: https://issues.redhat.com/browse/ISPN-11223 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 10.1.1.Final > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > Java11 added the ExtendedSocketOptions. > See http://hg.openjdk.java.net/jdk/jdk/rev/7164c3bb55df as a reference. > The class TcpKeepAliveTest has good examples how this should be configured -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11223) Support tcp_keepalive_time, tcp_keepalive_intvl, tcp_keepalive_probes for our (HotRod|Rest) clients

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11223?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11223: ------------------------------------------ Fix Version/s: 11.0.0.Final > Support tcp_keepalive_time, tcp_keepalive_intvl, tcp_keepalive_probes for our (HotRod|Rest) clients > --------------------------------------------------------------------------------------------------- > > Key: ISPN-11223 > URL: https://issues.redhat.com/browse/ISPN-11223 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 10.1.1.Final > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 11.0.0.Final > > > Java11 added the ExtendedSocketOptions. > See http://hg.openjdk.java.net/jdk/jdk/rev/7164c3bb55df as a reference. > The class TcpKeepAliveTest has good examples how this should be configured -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 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 2020