April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6412) RESTReplicationIT fails

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6412?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6412: ------------------------------------------- I'm not sure about this but the fix is really simple, so let's check it out! In theory Surefire should spawn a new JVM per each test and therefore we should always have a clean {{RESTHelper.servers}} instance. But I think [~mgencur] works on some domain tests, so fixing this (so that each test cleans the server list) might be a good idea. I'll create a PR and rebuild a couple of times on CI before marking ready for review. BTW - good eye Dan! > RESTReplicationIT fails > ----------------------- > > Key: ISPN-6412 > URL: https://issues.jboss.org/browse/ISPN-6412 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > http://ci.infinispan.org/viewLog.html?buildId=37653&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6436: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4226 > Overriding the name of an indexed property is not supported with DSL query > -------------------------------------------------------------------------- > > Key: ISPN-6436 > URL: https://issues.jboss.org/browse/ISPN-6436 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > If @Field(name="xyz") is used on an object property to customize the property name this will lead to the property not being found by the parser. The parser still looks for it using the java-beans naming conventions and ignores the 'name' attribute of the annotation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6477?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6477: ------------------------------------ I gave up on changing {{unregisterCacheMBean()}} because {{cache.stop()}} removes the cache's component registry from the global registry, and I didn't want to add more special cases. > Security tests always log a warning during cache manager shutdown > ----------------------------------------------------------------- > > Key: ISPN-6477 > URL: https://issues.jboss.org/browse/ISPN-6477 > Project: Infinispan > Issue Type: Bug > Components: Security, Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha1 > > > The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: > {noformat} > 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 > org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > {noformat} > {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. > {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6477?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6477: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4224 > Security tests always log a warning during cache manager shutdown > ----------------------------------------------------------------- > > Key: ISPN-6477 > URL: https://issues.jboss.org/browse/ISPN-6477 > Project: Infinispan > Issue Type: Bug > Components: Security, Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha1 > > > The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: > {noformat} > 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 > org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > {noformat} > {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. > {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6477?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6477: ------------------------------- Status: Open (was: New) > Security tests always log a warning during cache manager shutdown > ----------------------------------------------------------------- > > Key: ISPN-6477 > URL: https://issues.jboss.org/browse/ISPN-6477 > Project: Infinispan > Issue Type: Bug > Components: Security, Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha1 > > > The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: > {noformat} > 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 > org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > {noformat} > {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. > {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6471) Avoid blocking on Netty IO threads

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6471?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6471: ----------------------------------------- I've sent a PR to avoid using IO threads, relying on netty internal executor https://github.com/infinispan/infinispan/pull/4217 > Avoid blocking on Netty IO threads > ---------------------------------- > > Key: ISPN-6471 > URL: https://issues.jboss.org/browse/ISPN-6471 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > > Currently all cache operations are being executed in the {{NioEventLoopGroup}}. > Threads from this event loop group are responsible to process IO events from one or more channels and if it's blocked by one cache operation, all channels will stop processing events. > We should not block on IO threads but rather on a separate executor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6477: ---------------------------------- Summary: Security tests always log a warning during cache manager shutdown Key: ISPN-6477 URL: https://issues.jboss.org/browse/ISPN-6477 Project: Infinispan Issue Type: Bug Components: Security, Test Suite - Core Affects Versions: 8.2.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 9.0.0.Alpha1 The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: {noformat} 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] {noformat} {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6471) Avoid blocking on Netty IO threads

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6471?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-6471: ---------------------------------------- Isn't this a duplicate of ISPN-5083 ? > Avoid blocking on Netty IO threads > ---------------------------------- > > Key: ISPN-6471 > URL: https://issues.jboss.org/browse/ISPN-6471 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Gustavo Fernandes > > Currently all cache operations are being executed in the {{NioEventLoopGroup}}. > Threads from this event loop group are responsible to process IO events from one or more channels and if it's blocked by one cache operation, all channels will stop processing events. > We should not block on IO threads but rather on a separate executor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6466) Partition handling support on invalidation caches

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6466?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6466: ------------------------------------- Assignee: Dan Berindei > Partition handling support on invalidation caches > ------------------------------------------------- > > Key: ISPN-6466 > URL: https://issues.jboss.org/browse/ISPN-6466 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.2.5.Final > Reporter: Diego del Río > Assignee: Dan Berindei > Labels: partition_handling, split_brain > > See [this post | https://developer.jboss.org/message/953788] for a background discussion around this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6457) Servers should disallow access to internal user caches over the wire when authorization is disabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6457?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6457: --------------------------------------- Secure by default is quite important. Apparently it's ok if we allow access over loopback. > Servers should disallow access to internal user caches over the wire when authorization is disabled > --------------------------------------------------------------------------------------------------- > > Key: ISPN-6457 > URL: https://issues.jboss.org/browse/ISPN-6457 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > The server protocols currently allow access to internal user caches (such as the script and schema caches) if authorization is disabled. We should instead not allow access. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016