September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-3810) Clarify root README to state the multiple licensing

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-3810?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-3810. ----------------------------- Resolution: Out of Date > Clarify root README to state the multiple licensing > --------------------------------------------------- > > Key: ISPN-3810 > URL: https://issues.jboss.org/browse/ISPN-3810 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Sanne GRINOVERO > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5090) Reference documentation still refers to Infinispan 6 configuration examples

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-5090?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-5090. ----------------------------- Resolution: Out of Date > Reference documentation still refers to Infinispan 6 configuration examples > ---------------------------------------------------------------------------- > > Key: ISPN-5090 > URL: https://issues.jboss.org/browse/ISPN-5090 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Reporter: Emmanuel Bernard > Priority: Major > > http://infinispan.org/docs/7.0.x/getting_started/getting_started.html#_ex... > look for namedCache -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5102) Latest documentation links needed

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-5102?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-5102. ----------------------------- Resolution: Out of Date > Latest documentation links needed > --------------------------------- > > Key: ISPN-5102 > URL: https://issues.jboss.org/browse/ISPN-5102 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Documentation-Query, Documentation-Servers > Reporter: Galder Zamarreño > Priority: Major > > Unless talking about a specific documentation release, all our documentation links should be of type: > http://infinispan.org/docs/latest/... > Instead of: > http://infinispan.org/docs/7.0.x... > This would avoid having to keep constantly updating versions in our documentation, and also for blog posts. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5862) Add version number to deprecated comments

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-5862?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-5862. ----------------------------- Resolution: Out of Date > Add version number to deprecated comments > ----------------------------------------- > > Key: ISPN-5862 > URL: https://issues.jboss.org/browse/ISPN-5862 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 8.1.0.Alpha1 > Reporter: Dan Berindei > Priority: Major > > It should be possible to remove deprecated classes and methods after one major version cycle, but it's not always obvious when the API was deprecated. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5661) There are a number of broken links in the docs that contain {infinispanversion}

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-5661?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-5661. ----------------------------- Resolution: Out of Date > There are a number of broken links in the docs that contain {infinispanversion} > ------------------------------------------------------------------------------- > > Key: ISPN-5661 > URL: https://issues.jboss.org/browse/ISPN-5661 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 8.0.0.Beta2 > Reporter: Alan Field > Priority: Major > > I initially found an instance of the text {infinispanversion} in the properties file configuration example of section 13.4.3. Java Hot Rod client. However, if you search for that string, there are a number of links to the API docs that are not rendered as links and contain that text. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10428) Document declarative configuration of file-stores

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10428?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10428: ------------------------------- Component/s: Documentation-Servers (was: Core) (was: Server) > Document declarative configuration of file-stores > ------------------------------------------------- > > Key: ISPN-10428 > URL: https://issues.jboss.org/browse/ISPN-10428 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Environment: XSD > jboss-infinispan-core*.xsd > infinispan-config*.xsd > Reporter: Wolf-Dieter Fink > Assignee: Donald Naro > Priority: Minor > > Embedded and server mode are using a different configuration for file-store > embedded : infinispan-config* > {code} > </xs:attribute> > <xs:attribute name="relative-to" type="xs:string"> > <xs:annotation><xs:documentation>Unused XML attribute</xs:documentation></xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > </xs:extension> > </xs:complexContent> > </xs:complexType> > {code} > Here the relative-to is not used but referenced for path. > But path is used relative to PWD if it is not an absolute one, also if defaults to 'Infinispan-SingleFileStore' if not set. > For the server configuration it is > {code} > <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir"> > <xs:annotation> > <xs:documentation>The base directory in which to store the cache state.</xs:documentation> > </xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > But relative-to is a reference to a path declaration like this > {code} > <paths> > <path name="my.dir" path="/MyCacheStore"/> > </paths> > ... > <distributed-cache name="wolf"> > <persistence> > <file-store shared="false" fetch-state="true" relative-to="my.dir"/> > </persistence> > </distributed-cache> > {code} > If relative-to is set to a real path or env variable the server start will fail with > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.wolf.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.wolf.config: Failed to start service > ... > Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/MyCacheStore' > at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:765) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:760) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:58) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1517) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1503) > at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:55) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10598) Docs: Endpoint authentication and encryption

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10598?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10598: ------------------------------- Sprint: DataGrid Sprint #35 > Docs: Endpoint authentication and encryption > -------------------------------------------- > > Key: ISPN-10598 > URL: https://issues.jboss.org/browse/ISPN-10598 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10564) Docs: Remove Wildfly/EAP content from 10.x

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10564?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10564: ------------------------------- Sprint: DataGrid Sprint #35 (was: DataGrid Sprint #34) > Docs: Remove Wildfly/EAP content from 10.x > ------------------------------------------ > > Key: ISPN-10564 > URL: https://issues.jboss.org/browse/ISPN-10564 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need to remove wildfly/eap attributes from product-attributes.adoc and pom.xml. Also need to remove old references to wildfly/eap functionality like the server modules, etc. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4610) Implement total order for non-transactional caches

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-4610?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4610: ------------------------------ Priority: Optional (was: Major) > Implement total order for non-transactional caches > -------------------------------------------------- > > Key: ISPN-4610 > URL: https://issues.jboss.org/browse/ISPN-4610 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Alpha5 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Optional > > Current locking algorithm in non-transactional caches needs a remote thread on the primary owner to block while replicating the update to the backup owner. The thread is also holding the lock for the key, so it's blocking other threads that want to write to the same key. When there is a lot of contention, this can exhaust the remote executor thread pool and cause lock timeouts. > TO was designed with high contention in mind, and it doesn't block threads to acquire locks. So it should handle this much better. > An alternative solution would be the locking rework in ISPN-2849. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3189) Extend Grouping API to mapping of DeltaCompositeKeys to the same node as the delta aware value key

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-3189?page=com.atlassian.jira.plugin.... ] Pedro Ruivo closed ISPN-3189. ----------------------------- Resolution: Out of Date {{DeltaCompositeKey}} was removed. > Extend Grouping API to mapping of DeltaCompositeKeys to the same node as the delta aware value key > -------------------------------------------------------------------------------------------------- > > Key: ISPN-3189 > URL: https://issues.jboss.org/browse/ISPN-3189 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 5.3.0.CR1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > > Try to understand and analyze the performance impact to extended the Grouping API to support the DeltaCompositeKey and return the owners based on the delta aware value key. > In the current implementation, the interceptors are responsible to check if the key is a DeltaCompositeKey instance and check for the ownership based on the delta aware value key. > Pros and cons of using an extension of Grouping API > Pros: > * this check for DeltaCompositeKey instance is done in a single point instead of being spread in the code. > * less error prone > Cons: > * possible performance impact since all the getSegment(key) invocations should perform the check. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 7 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 September 2019