October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10592) Remove deprecated ComponentMetadata, ComponentMetadataRepo, ManageableComponentMetadata

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10592?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10592: --------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35) > Remove deprecated ComponentMetadata, ComponentMetadataRepo, ManageableComponentMetadata > --------------------------------------------------------------------------------------- > > Key: ISPN-10592 > URL: https://issues.jboss.org/browse/ISPN-10592 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > > These are leftovers of the old component registry that are no longer used. They no longer work because the retention of the annotations is no longer RUNTIME. Keeping them for now for backward compatibility is a waste of effort that does not lead to working code, just clutters existing code base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10642) Docs: Update server health with new cli and REST v2

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10642?page=com.atlassian.jira.plugin... ] Work on ISPN-10642 started by Donald Naro. ------------------------------------------ > Docs: Update server health with new cli and REST v2 > --------------------------------------------------- > > Key: ISPN-10642 > URL: https://issues.jboss.org/browse/ISPN-10642 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Server guide. Need to update the examples for server health via CLI and REST server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10642) Docs: Update server health with new cli and REST v2

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10642?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10642: ------------------------------- Status: Open (was: New) > Docs: Update server health with new cli and REST v2 > --------------------------------------------------- > > Key: ISPN-10642 > URL: https://issues.jboss.org/browse/ISPN-10642 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Server guide. Need to update the examples for server health via CLI and REST server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10512) Docs: CLI

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10512?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10512: ------------------------------- Description: Use asciidoc man pages for commands as reference content. Add examples for CLI usage: using the schemas resource to hide protobuf metadata cache query paging counters batch from stdin xsite commands TLS support was: As a user, I need to connect to remote server instances via the CLI. As a user, I need to find CLI help text and understand basic command syntax. > Docs: CLI > --------- > > Key: ISPN-10512 > URL: https://issues.jboss.org/browse/ISPN-10512 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Use asciidoc man pages for commands as reference content. > Add examples for CLI usage: > using the schemas resource to hide protobuf metadata cache > query paging > counters > batch from stdin > xsite commands > TLS support -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10724) Ignored caches per server causes a performance regression

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10724?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10724: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7412 > Ignored caches per server causes a performance regression > --------------------------------------------------------- > > Key: ISPN-10724 > URL: https://issues.jboss.org/browse/ISPN-10724 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Gustavo Fernandes > Priority: Critical > > https://issues.jboss.org/browse/ISPN-10552 reduce the performance throughput from 20k to 4.5k operations per second > Commit: https://github.com/infinispan/infinispan/commit/ce23665b7d4424d91d9a3c4de... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10745) infinispan-jcache-remote does not support CDI caching annotations

by Dan Berindei (Jira)

Dan Berindei created ISPN-10745: ----------------------------------- Summary: infinispan-jcache-remote does not support CDI caching annotations Key: ISPN-10745 URL: https://issues.jboss.org/browse/ISPN-10745 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.0.0.CR3, 9.4.16.Final Reporter: Dan Berindei {{infinispan-jcache-remote}} does not have CDI interceptors for the JCache annotations like {{@CacheResult}}, so the annotations are ignored. The JCache TCK has tests for the annotations (e.g. {{InterceptionCacheNameOnEachMethodTest}}), but those tests used to pass by accident: a Weld dependency ({{slf4j-api}}) was missing in the {{tck-remote}} maven-failsafe-plugin execution, and {{AbstractInterceptionTest}} was automatically excluding them. Weld 2.3.4.Final removed the {{slf4j-api}} dependency and the {{tck-remote}} interception tests started failing after the upgrade, but we did not notice because of ISPN-10379. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10745) infinispan-jcache-remote does not support CDI caching annotations

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10745?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10745: -------------------------------- Status: Open (was: New) > infinispan-jcache-remote does not support CDI caching annotations > ----------------------------------------------------------------- > > Key: ISPN-10745 > URL: https://issues.jboss.org/browse/ISPN-10745 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Priority: Major > > {{infinispan-jcache-remote}} does not have CDI interceptors for the JCache annotations like {{@CacheResult}}, so the annotations are ignored. > The JCache TCK has tests for the annotations (e.g. {{InterceptionCacheNameOnEachMethodTest}}), but those tests used to pass by accident: a Weld dependency ({{slf4j-api}}) was missing in the {{tck-remote}} maven-failsafe-plugin execution, and {{AbstractInterceptionTest}} was automatically excluding them. > Weld 2.3.4.Final removed the {{slf4j-api}} dependency and the {{tck-remote}} interception tests started failing after the upgrade, but we did not notice because of ISPN-10379. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10666) Eviction get stuck with <off-heap> configuration and optimistic transactions

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10666?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10666: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 (was: 10.0.0.Final) Resolution: Done > Eviction get stuck with <off-heap> configuration and optimistic transactions > ---------------------------------------------------------------------------- > > Key: ISPN-10666 > URL: https://issues.jboss.org/browse/ISPN-10666 > Project: Infinispan > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Fix For: 9.4.17.Final, 10.0.0.CR3 > > > If the cache is configured as followed adding entries every second will end up in an unresponsive server. > The client will stop after 120sec (eviction count reached) with > Exception in thread "main" org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: PutOperation{ExpirationCache, key=[B0x033E17323031392D..[26], value=[B0x033F280058585858..[10244], flags=4} timed out after 60000 ms > at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54) > at org.infinispan.client.hotrod.impl.Util.await(Util.java:27) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:335) > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:129) > at org.infinispan.wfink.hotrod.client.HotRodConstantLoadExpirationClient.putWithExpiration(HotRodConstantLoadExpirationClient.java:48) > at org.infinispan.wfink.hotrod.client.HotRodConstantLoadExpirationClient.testLoop(HotRodConstantLoadExpirationClient.java:84) > at org.infinispan.wfink.hotrod.client.HotRodConstantLoadExpirationClient.main(HotRodConstantLoadExpirationClient.java:160) > Caused by: java.net.SocketTimeoutException: PutOperation{ExpirationCache, key=[B0x033E17323031392D..[26], value=[B0x033F280058585858..[10244], flags=4} timed out after 60000 ms > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172) > at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) > at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127) > at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322) > at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10650) Expiration should not be replicated cross site

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10650?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10650: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 (was: 10.0.0.Final) Resolution: Done > Expiration should not be replicated cross site > ---------------------------------------------- > > Key: ISPN-10650 > URL: https://issues.jboss.org/browse/ISPN-10650 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Expiration > Affects Versions: 9.4.16.Final, 10.0.0.CR2 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 9.4.17.Final, 10.0.0.CR3 > > > There is no reason currently to replicate expiration commands across site. > Lifespan will work just fine without without replicating as the entry is expired on either side properly, irrespective of system clocks. > However max idle doesn't support the given semantics with xsite. We currently only confirm from other nodes in the same cluster for max idle before removing. It would be extremely costly to query all the cross sites to see if they have a read on the same entry before expiring. Also this requires having system clocks somewhat close in time, which can be even more problematic with clusters in disparate locations. We need to document that this doesn't work as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10618: ------------------------------- Fix Version/s: 10.0.0.CR3 (was: 10.0.0.Final) > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

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