February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9937) Fix Linking to Spring Classes

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9937?page=com.atlassian.jira.plugin.... ] Don Naro updated ISPN-9937: --------------------------- Status: Open (was: New) > Fix Linking to Spring Classes > ----------------------------- > > Key: ISPN-9937 > URL: https://issues.jboss.org/browse/ISPN-9937 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Affects Versions: 10.0.0.Beta1, 9.4.7.Final > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > Removing linking to Javadocs in Spring Integration topic. > * link:{javadocroot}/org/infinispan/spring/provider/SpringEmbeddedCacheManagerFactoryBean.html[SpringEmbeddedCacheManagerFactoryBean] > * link:{javadocroot}/org/infinispan/spring/provider/SpringRemoteCacheManagerFactoryBean.html[SpringRemoteCacheManagerFactoryBean] > in documentation/src/main/asciidoc/user_guide/integrations_spring.adoc > results in 404. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9905) Rest store should retrieve created and lastUsed TS from server

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9905?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9905. -------------------------------- Resolution: Done > Rest store should retrieve created and lastUsed TS from server > -------------------------------------------------------------- > > Key: ISPN-9905 > URL: https://issues.jboss.org/browse/ISPN-9905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 10.0.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently the rest store simply sets the created and lastUsed entries to the current time of the node loading an entry, instead we should retrieve this value from the server if fetchMetadata is true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9908) Cache startup failure with server hinting and insufficient segments

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9908?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9908: ------------------------------- Summary: Cache startup failure with server hinting and insufficient segments (was: Cache startup failure with insufficient segments) > Cache startup failure with server hinting and insufficient segments > ------------------------------------------------------------------- > > Key: ISPN-9908 > URL: https://issues.jboss.org/browse/ISPN-9908 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.6.Final > Reporter: Hiroki Daicho > Assignee: Dan Berindei > Priority: Major > Attachments: logs.zip > > > When setting small segment to a cache and using server hinting, node can't start with the following error[1]. > It can be reproduced with RHDG 7.2.3 and 7.3 ER2. > [1] > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.test: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.test: Failed to start service > ... > Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl > ... > Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for svr01 (flags=0), site-id=site1, rack-id=rack1, machine-id=machine1) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:916) > ... > {code} > For example, 3rd node will fail to start with the following setting in 3 nodes cluster. > When set the segments to 20 (6.6.2 default), 6th node will fail to start with the above timeout. > Nodes seems to not be able to finish the initial state transfer and start up fails if the segments are set insufficiently against the number of nodes, > {code} > <distributed-cache name="default" segments="1" /> > ... > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp" machine="${jboss.jgroups.transport.machine:machine1}" rack="${jboss.jgroups.transport.rack:rack1}" site="${jboss.jgroups.transport.site:site1}" /> > </stack> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6662, https://github.com/infinispan/infinispan/pull/6663 (was: https://github.com/infinispan/infinispan/pull/6662) > Warning instead if exception with 0 capacity node and clustered locks > --------------------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6662 > Warning instead if exception with 0 capacity node and clustered locks > --------------------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Work on ISPN-9921 started by Katia Aresti. ------------------------------------------ > Warning instead if exception with 0 capacity node and clustered locks > --------------------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9921: ------------------------------- Status: Open (was: New) > Warning instead if exception with 0 capacity node and clustered locks > --------------------------------------------------------------------- > > Key: ISPN-9921 > URL: https://issues.jboss.org/browse/ISPN-9921 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1 > > > If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario. > Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9938) Provide a proper and cache specific semantics new API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9938?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9938: ------------------------------- Summary: Provide a proper and cache specific semantics new API (was: Provide a proper and cache only semantics new API) > Provide a proper and cache specific semantics new API > ----------------------------------------------------- > > Key: ISPN-9938 > URL: https://issues.jboss.org/browse/ISPN-9938 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Galder Zamarreño > Priority: Major > > Caffeine or Cache2K are good examples of concise and cache semantic specific API. > Provide this new API interface -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9938) Provide a proper and cache only semantics new API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9938?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9938: ------------------------------- Summary: Provide a proper and cache only semantics new API (was: Provide a good only cache semantics new API) > Provide a proper and cache only semantics new API > ------------------------------------------------- > > Key: ISPN-9938 > URL: https://issues.jboss.org/browse/ISPN-9938 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Galder Zamarreño > Priority: Major > > Caffeine or Cache2K are good examples of concise and cache semantic specific API. > Provide this new API interface -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9938) Provide a good only cache semantics new API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9938?page=com.atlassian.jira.plugin.... ] Katia Aresti reassigned ISPN-9938: ---------------------------------- Assignee: Galder Zamarreño > Provide a good only cache semantics new API > ------------------------------------------- > > Key: ISPN-9938 > URL: https://issues.jboss.org/browse/ISPN-9938 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Galder Zamarreño > Priority: Major > > Caffeine or Cache2K are good examples of concise and cache semantic specific API. > Provide this new API interface -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019