[JBoss JIRA] (ISPN-10377) listener CacheEntryExpired callback , key is not locked
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10377?page=com.atlassian.jira.plugin... ]
Tristan Tarrant reassigned ISPN-10377:
--------------------------------------
Assignee: Will Burns
> listener CacheEntryExpired callback , key is not locked
> -------------------------------------------------------
>
> Key: ISPN-10377
> URL: https://issues.jboss.org/browse/ISPN-10377
> Project: Infinispan
> Issue Type: Bug
> Components: API
> Affects Versions: 9.4.15.Final
> Reporter: Alexander Malysh
> Assignee: Will Burns
> Priority: Major
> Attachments: CacheTest1.java, infinispan-test.xml
>
>
> Hi,
> it looks like that CacheEntryExpired callback is called without a key lock held like CacheEntryRemoved. In this scenario I'm unable to synchronize keys if reaper thread is enabled.
> I'm attaching simple test case that will show this issue. Because it's a classical race condition please start this test multiple times if result should be ok.
> Thanks in advance!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-8736) REST endpoint authorization
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-8736?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8736:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> REST endpoint authorization
> ---------------------------
>
> Key: ISPN-8736
> URL: https://issues.jboss.org/browse/ISPN-8736
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST, Security, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> The REST endpoint does not use the authenticated user to access authz caches. We need to:
> - integrate with the ServerAuthenticationProvider as used by the Hot Rod endpoint so that we can use security callbacks and retrieve a fully populated subject (including groups). This should ultimately connect with Elytron.
> - add SecurityActions within the rest code
> - Return 403 forbidden where needed
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10384) Create dedicated maven-plugins repository
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10384?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10384:
--------------------------------
Description:
In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser.
We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code.
The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons.
https://github.com/infinispan/maven-plugins
was:
In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser.
We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code.
The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons.
> Create dedicated maven-plugins repository
> -----------------------------------------
>
> Key: ISPN-10384
> URL: https://issues.jboss.org/browse/ISPN-10384
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build
> Affects Versions: 10.0.0.Beta3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta4
>
>
> In the main ISPN repo we have a plugins dir that contains our custom maven plugins used throughout our builds. Currently this dir contains the infinispan-defaults-maven-plugin for extracting code defaults to xsd and the protocol-parser-generator-maven-plugin for generating the hotrod parser.
> We should create a new repository under the infinispan org, e.g. github.com/infinispan/maven-plugins, to contain all of our maven plugins that do not depend on ISPN code.
> The infinispan-defaults-maven-plugin can't be moved as it depends on infinispan-commons.
> https://github.com/infinispan/maven-plugins
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months