October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9630) Spring Session contains {brandname} into the class name

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9630?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9630: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done integrated > Spring Session contains {brandname} into the class name > ------------------------------------------------------- > > Key: ISPN-9630 > URL: https://issues.jboss.org/browse/ISPN-9630 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > In the docs we have > Spring Session integration has been based on {brandname} Spring Cache support so it requires creating a `SpringEmbeddedCacheManagerFactoryBean` or `SpringRemoteCacheManagerFactoryBean`. > The next step it to use `@Enable{brandname}EmbeddedHttpSession` or `@Enable{brandname}RemoteHttpSession` configuration annotation which turns on Spring Session. > It should be > @EnableInfinispanEmbeddedHttpSession > @EnableInfinispanRemoteHttpSession -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5319) TreeCache with concurrent puts becomes inconsistent

by Jeremy Stone (Jira)

[ https://issues.jboss.org/browse/ISPN-5319?page=com.atlassian.jira.plugin.... ] Jeremy Stone commented on ISPN-5319: ------------------------------------ Any updates on this one? > TreeCache with concurrent puts becomes inconsistent > --------------------------------------------------- > > Key: ISPN-5319 > URL: https://issues.jboss.org/browse/ISPN-5319 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 7.2.0.Final > Reporter: Jeremy Stone > Priority: Major > > Concurrent puts using tree cache api store data values in the tree but the structure of tree can become corrupted. Namely: node.getChildren() for a parent node might not include the child node even though the child node exists and has some data. > This makes it difficult to reliably use the tree cache structure to mirror a corresponding tree-like business data structure (e.g. materialized from a database). > This can be readily reproduced with a local cache. A unit test is attached to the referenced forum topic. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9618) Overlay for Java 10 could be Java 9

by tommaso borgato (Jira)

[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ] tommaso borgato commented on ISPN-9618: --------------------------------------- [~NadirX] why, then, to code overlays for versions that are unsupported? > Overlay for Java 10 could be Java 9 > ----------------------------------- > > Key: ISPN-9618 > URL: https://issues.jboss.org/browse/ISPN-9618 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.4.0.Final > Reporter: tommaso borgato > Priority: Major > > The following classes are in overlay for Java 10: > - commons/src/main/java10/org/infinispan/commons/jdkspecific/CallerId.java > - commons/src/main/java10/org/infinispan/commons/jdkspecific/ProcessorInfo.java > CallerId uses StackWalker that is available since Java 9. > ProcessorInfo uses Runtime.getRuntime().availableProcessors() that was fixed in java 9 (https://bugs.java.com/view_bug.do?bug_id=6515172) > Question: can those classes be in overlay for Java 9 instead of Java 10 ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9509) OffHeapConcurentMap can throw exception during shutdown

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9509?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9509. ------------------------------- > OffHeapConcurentMap can throw exception during shutdown > ------------------------------------------------------- > > Key: ISPN-9509 > URL: https://issues.jboss.org/browse/ISPN-9509 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.0.CR3 > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.0.CR3 > > > This exception can occur when shutting down. We should ensure that they are shut down in proper order. Maybe even allow clear to do nothing for `OffHeapConcurrentMap` when it is deallocated. > {code} > 15:38:39,796 WARN [org.infinispan.factories.ComponentRegistry] (MSC service thread 1-6) ISPN000189: While stopping a cache or cache manager, one of its components failed to stop: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.container.offheap.OffHeapDataContainer.clear() on object of type OffHeapDataContainer > 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$internalStop$7(AbstractComponentRegistry.java:741) > at org.infinispan.factories.SecurityActions.lambda$run$1(SecurityActions.java:72) > at org.infinispan.security.Security.doPrivileged(Security.java:49) > at org.infinispan.factories.SecurityActions.run(SecurityActions.java:71) > at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:734) > at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:639) > at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:271) > at org.infinispan.cache.impl.CacheImpl.performImmediateShutdown(CacheImpl.java:1095) > at org.infinispan.cache.impl.CacheImpl.stop(CacheImpl.java:1060) > at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:460) > at org.infinispan.server.infinispan.SecurityActions.lambda$stopCache$5(SecurityActions.java:131) > at org.infinispan.security.Security.doPrivileged(Security.java:44) > at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:69) > at org.infinispan.server.infinispan.SecurityActions.stopCache(SecurityActions.java:134) > at org.jboss.as.clustering.infinispan.subsystem.CacheService.stop(CacheService.java:108) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1792) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1761) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Map was already shut down! > at org.infinispan.container.offheap.OffHeapConcurrentMap.checkDeallocation(OffHeapConcurrentMap.java:143) > at org.infinispan.container.offheap.OffHeapConcurrentMap.clear(OffHeapConcurrentMap.java:502) > at org.infinispan.container.offheap.OffHeapDataContainer.clear(OffHeapDataContainer.java:127) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.infinispan.commons.util.SecurityActions.lambda$invokeAccessibly$0(SecurityActions.java:79) > ... 27 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9415) Client topology is not updated after cache becomes degraded

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9415?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9415: -------------------------------- Labels: on-hold (was: ) > Client topology is not updated after cache becomes degraded > ----------------------------------------------------------- > > Key: ISPN-9415 > URL: https://issues.jboss.org/browse/ISPN-9415 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.0.Beta1, 9.3.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3 > > > When a new server is started, or after a merge, the other servers may see it as a an owner in the consistent hash before the other servers see its server address in the address cache ({{___hotRodTopologyCache}}). When a server needs to send a topology update but some of the servers are missing from the address cache, it can't send the topology update, so it tries to send a "partial update" that excludes the missing servers from the segment owners. In order to send the full topology update when the address cache is populated, the partial topology update has to be sent a smaller topology id, and that means it is only send if {{serverTopologyId >= clientTopologyId + 2}}. > When the cluster splits and the cache becomes degraded, the servers in the other partition are removed from the address cache, but the list of segment owners is not updated, and the topology id is only incremented by 1. The address cache is incomplete, but a partial update cannot be sent, so the client keeps the old topology and keeps trying to connect to the servers in the other partition. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9301) Add read timeout configuration to the Spring Cache provider

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9301?page=com.atlassian.jira.plugin.... ] Diego Lovison closed ISPN-9301. ------------------------------- > Add read timeout configuration to the Spring Cache provider > ----------------------------------------------------------- > > Key: ISPN-9301 > URL: https://issues.jboss.org/browse/ISPN-9301 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Spring Integration > Affects Versions: 9.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.0.Alpha1, 9.4.0.CR3 > > > The Spring Cache provider has no distinction between sync and async calls. In a cache scenario with fail-fast semantics it is desirable to fail a read operation when it doesn't complete within a specified timeout. > We should add a configuration property which implements this -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9630) Spring Session contains {brandname} into the class name

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9630?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9630: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6348/files > Spring Session contains {brandname} into the class name > ------------------------------------------------------- > > Key: ISPN-9630 > URL: https://issues.jboss.org/browse/ISPN-9630 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Priority: Major > > In the docs we have > Spring Session integration has been based on {brandname} Spring Cache support so it requires creating a `SpringEmbeddedCacheManagerFactoryBean` or `SpringRemoteCacheManagerFactoryBean`. > The next step it to use `@Enable{brandname}EmbeddedHttpSession` or `@Enable{brandname}RemoteHttpSession` configuration annotation which turns on Spring Session. > It should be > @EnableInfinispanEmbeddedHttpSession > @EnableInfinispanRemoteHttpSession -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9630) Spring Session contains {brandname} into the class name

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9630?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9630: -------------------------------- Status: Open (was: New) > Spring Session contains {brandname} into the class name > ------------------------------------------------------- > > Key: ISPN-9630 > URL: https://issues.jboss.org/browse/ISPN-9630 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Priority: Major > > In the docs we have > Spring Session integration has been based on {brandname} Spring Cache support so it requires creating a `SpringEmbeddedCacheManagerFactoryBean` or `SpringRemoteCacheManagerFactoryBean`. > The next step it to use `@Enable{brandname}EmbeddedHttpSession` or `@Enable{brandname}RemoteHttpSession` configuration annotation which turns on Spring Session. > It should be > @EnableInfinispanEmbeddedHttpSession > @EnableInfinispanRemoteHttpSession -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9630) Spring Session contains {brandname} into the class name

by Diego Lovison (Jira)

Diego Lovison created ISPN-9630: ----------------------------------- Summary: Spring Session contains {brandname} into the class name Key: ISPN-9630 URL: https://issues.jboss.org/browse/ISPN-9630 Project: Infinispan Issue Type: Bug Reporter: Diego Lovison In the docs we have Spring Session integration has been based on {brandname} Spring Cache support so it requires creating a `SpringEmbeddedCacheManagerFactoryBean` or `SpringRemoteCacheManagerFactoryBean`. The next step it to use `@Enable{brandname}EmbeddedHttpSession` or `@Enable{brandname}RemoteHttpSession` configuration annotation which turns on Spring Session. It should be @EnableInfinispanEmbeddedHttpSession @EnableInfinispanRemoteHttpSession -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9301) Add read timeout configuration to the Spring Cache provider

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9301?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9301: -------------------------------- Tester: Diego Lovison > Add read timeout configuration to the Spring Cache provider > ----------------------------------------------------------- > > Key: ISPN-9301 > URL: https://issues.jboss.org/browse/ISPN-9301 > Project: Infinispan > Issue Type: Feature Request > Components: Hot Rod, Spring Integration > Affects Versions: 9.2.4.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.0.Alpha1, 9.4.0.CR3 > > > The Spring Cache provider has no distinction between sync and async calls. In a cache scenario with fail-fast semantics it is desirable to fail a read operation when it doesn't complete within a specified timeout. > We should add a configuration property which implements this -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 2018