October 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9067) Tests should set the node name even for non-clustered cache manager

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9067?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9067: -------------------------------- Labels: on-hold (was: ) > Tests should set the node name even for non-clustered cache manager > ------------------------------------------------------------------- > > Key: ISPN-9067 > URL: https://issues.jboss.org/browse/ISPN-9067 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: on-hold > Fix For: 9.4.0.CR3 > > > The node name is included in the thread name by all the internal executors, but non-clustered cache managers don't have a node name, and that makes it harder to filter log messages for a particular test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9632) PersistenceManager should be able to start if store's are unavailable

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-9632: ---------------------------------- Summary: PersistenceManager should be able to start if store's are unavailable Key: ISPN-9632 URL: https://issues.jboss.org/browse/ISPN-9632 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 9.4.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Alpha1 Currently it is necessary for a store to become available before `connection-attempts` are exceeded, otherwise cache startup fails. It should be possible for the PM to still start without the store being available, with the store's unavailability logged and operations requiring persistence still throwing StoreUnavailableException messages unless `SKIP_CACHE_STORE`/`SKIP_CACHE_LOAD` flags are present. Cache startup should still fail if preload=true as this behaviour is not possible if the store is unavailable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9631?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9631: ------------------------------- Description: The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. AbstractOperations::createResponseException should be modified. was:The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present > REST API should return 503 Service Unavailable if store's becomes unavailable > ----------------------------------------------------------------------------- > > Key: ISPN-9631 > URL: https://issues.jboss.org/browse/ISPN-9631 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. > AbstractOperations::createResponseException should be modified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-9631: ---------------------------------- Summary: REST API should return 503 Service Unavailable if store's becomes unavailable Key: ISPN-9631 URL: https://issues.jboss.org/browse/ISPN-9631 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores, REST Affects Versions: 9.4.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Alpha1 The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present -- 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 Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9618: --------------------------------------- That is handled by ISPN-9628 which has PRs for 9.4 and 9.3 > 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-9618) Overlay for Java 10 could be Java 9

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on ISPN-9618: ----------------------------------------- [~NadirX], thanks for explanation, 10 is valid option, to us it was a bit unusual as all other components we use go just with 9. There is still trouble that the infinispan-commons jar has overlay, but {{Multi-Release: true}} is not set in MANIFEST. So the overlay is not activated :( > 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-9618) Overlay for Java 10 could be Java 9

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9618: --------------------------------------- And in our case the "10" is there, because that was the version of Java with that feature that was supported it at the time > 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-9618) Overlay for Java 10 could be Java 9

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-9618: --------------------------------------- Java 9 went end-of-life when Java 10 was released. Java 10 went end-of-life when Java 11 was released. Java 11 is a long-term-support (LTS) release. The next LTS is hoped to be Java 14. > 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-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 reassigned ISPN-9630: ---------------------------------- Assignee: Katia Aresti > 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: Katia Aresti > 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 Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9630?page=com.atlassian.jira.plugin.... ] Katia Aresti reassigned ISPN-9630: ---------------------------------- Assignee: Diego Lovison (was: Katia Aresti) > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2018