December 2020 - infinispan-issues

[Red Hat JIRA] (ISPN-12301) Display a list of example entries when we land into the cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12301?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12301: -------------------------------- Fix Version/s: 12.0.0.Final > Display a list of example entries when we land into the cache > ------------------------------------------------------------- > > Key: ISPN-12301 > URL: https://issues.redhat.com/browse/ISPN-12301 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 12.0.0.Dev03 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > When we land into the cache detail, entries tab, display a sample of the data -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12301) Display a list of example entries when we land into the cache

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12301?page=com.atlassian.jira.plugi... ] Work on ISPN-12301 started by Katia Aresti. ------------------------------------------- > Display a list of example entries when we land into the cache > ------------------------------------------------------------- > > Key: ISPN-12301 > URL: https://issues.redhat.com/browse/ISPN-12301 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 12.0.0.Dev03 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > > When we land into the cache detail, entries tab, display a sample of the data -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Description: The REST endpoint that streams entries, does not convert lifespan and maxidle to seconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds (was: The REST endpoint that streams entries, does not convert lifespan and maxidle to secods, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds) > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams entries, does not convert lifespan and maxidle to seconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Description: The REST endpoint that streams entries, does not convert lifespan and maxidle to secods, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds (was: The REST endpoint that streams entries, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds) > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams entries, does not convert lifespan and maxidle to secods, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Description: The REST endpoint that streams entries, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds (was: The REST endpoint that streams key values, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds) > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams entries, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Status: Open (was: New) > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams key values, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8924 > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams key values, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12565?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12565: -------------------------------- Fix Version/s: 12.0.0.Final > Entries stream does not convert maxidle and lifespan to seconds > --------------------------------------------------------------- > > Key: ISPN-12565 > URL: https://issues.redhat.com/browse/ISPN-12565 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 12.0.0.Dev07 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 12.0.0.Final > > > The REST endpoint that streams key values, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-12565) Entries stream does not convert maxidle and lifespan to seconds

by Katia Aresti (Jira)

Katia Aresti created ISPN-12565: ----------------------------------- Summary: Entries stream does not convert maxidle and lifespan to seconds Key: ISPN-12565 URL: https://issues.redhat.com/browse/ISPN-12565 Project: Infinispan Issue Type: Bug Components: REST Affects Versions: 12.0.0.Dev07 Reporter: Katia Aresti Assignee: Katia Aresti The REST endpoint that streams key values, does not convert lifespan and maxidle to milliseconds, while the REST API works with those parameters with seconds even if internally they are stored as milliseconds -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

[Red Hat JIRA] (ISPN-9165) ManifestUberJarDuplicatedJarsWarner uses FJP without privileged block

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/ISPN-9165?page=com.atlassian.jira.plugin... ] Boris Unckel commented on ISPN-9165: ------------------------------------ [~dmlloyd] We had the same issue. Please find a possible solution attached. I don't have a stacktrace (anymore) and no unit test. It solved the issue for our productive system. The idea is similar to #2 in the description above. It seems with [ISPN-10274 Remove uberjar warnings|https://github.com/infinispan/infinispan/commit/6d598c530ab73539...] this is obsolete and the issue can be closed? > ManifestUberJarDuplicatedJarsWarner uses FJP without privileged block > --------------------------------------------------------------------- > > Key: ISPN-9165 > URL: https://issues.redhat.com/browse/ISPN-9165 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.2.Final > Reporter: David Lloyd > Priority: Critical > Labels: security-manager > Attachments: ManifestUberJarDuplicatedJarsWarner.java > > > {{ManifestUberJarDuplicatedJarsWarner}} has a method called {{isClasspathCorrectAsync}} which dispatches a task to the fork-join pool. The task loads resources from the Infinispan JAR. > This fails under a security manager. The common FJP executes tasks with no permissions. One of two things must be done: > # Do not use the fork-join pool; find some other async solution which preserves the access control context. > # Capture and propagate the current AccessControlContext when calling {{isClasspathCorrectAsync}}. This can be done by calling {{AccessController.getContext()}} before submitting the task, and then, within the submitted lambda, wrap the call to isClasspathCorrect with a call to {{AccessController.doPrivileged()}} which restores the captured context (by giving it as the second parameter). Note that this will entail a nested lambda or anonymous class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2020