[JBoss JIRA] (ISPN-8379) Support configuration wildcards
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8379?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8379:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5507
> Support configuration wildcards
> -------------------------------
>
> Key: ISPN-8379
> URL: https://issues.jboss.org/browse/ISPN-8379
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.2.0.Final
>
>
> Allow defining configuration names containing wildcards so that they are implicitly used for caches whose names match. This would be particularly useful for using templates with JCache which doesn't allow specifying additional configuration properties outside what is available in MutableConfiguration.
> Therefore, declaring a cache configuration such as:
> {code:xml}
> <invalidation-cache-configuration name="invalidation-*" />
> {code}
> and invoking:
> {code:java}
> cacheManager.getCache("invalidation-1");
> {code}
> would use the above configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8379) Support configuration wildcards
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8379?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8379:
----------------------------------
Status: Open (was: New)
> Support configuration wildcards
> -------------------------------
>
> Key: ISPN-8379
> URL: https://issues.jboss.org/browse/ISPN-8379
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.2.0.Final
>
>
> Allow defining configuration names containing wildcards so that they are implicitly used for caches whose names match. This would be particularly useful for using templates with JCache which doesn't allow specifying additional configuration properties outside what is available in MutableConfiguration.
> Therefore, declaring a cache configuration such as:
> {code:xml}
> <invalidation-cache-configuration name="invalidation-*" />
> {code}
> and invoking:
> {code:java}
> cacheManager.getCache("invalidation-1");
> {code}
> would use the above configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-8338:
-------------------------------------
[~anistor] Initially I just added start and had though about @Stop. I had forgotten Tristan just added @PostStart, but I can agree that we should do this for both of these as well.
> Cache start methods should run privileged
> -----------------------------------------
>
> Key: ISPN-8338
> URL: https://issues.jboss.org/browse/ISPN-8338
> Project: Infinispan
> Issue Type: Task
> Components: Security
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ]
William Burns edited comment on ISPN-8338 at 10/9/17 3:22 AM:
--------------------------------------------------------------
[~william.burns] Is this just for @Start? I think this would be nice for @PostStart and @Stop too.
was (Author: anistor):
[~william.burns]] Is this just for @Start? I think this would be nice for @PostStart and @Stop too.
> Cache start methods should run privileged
> -----------------------------------------
>
> Key: ISPN-8338
> URL: https://issues.jboss.org/browse/ISPN-8338
> Project: Infinispan
> Issue Type: Task
> Components: Security
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ]
William Burns edited comment on ISPN-8338 at 10/9/17 3:21 AM:
--------------------------------------------------------------
[~william.burns]] Is this just for @Start? I think this would be nice for @PostStart and @Stop too.
was (Author: anistor):
[~wburns] Is this just for @Start? I think this would be nice for @PostStart and @Stop too.
> Cache start methods should run privileged
> -----------------------------------------
>
> Key: ISPN-8338
> URL: https://issues.jboss.org/browse/ISPN-8338
> Project: Infinispan
> Issue Type: Task
> Components: Security
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8318) BulkOperationsTest.testBulkOperations failing randomly
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-8318?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-8318:
-----------------------------------
Component/s: Hibernate Cache
> BulkOperationsTest.testBulkOperations failing randomly
> ------------------------------------------------------
>
> Key: ISPN-8318
> URL: https://issues.jboss.org/browse/ISPN-8318
> Project: Infinispan
> Issue Type: Bug
> Components: Hibernate Cache
> Affects Versions: 9.1.0.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 9.2.0.Alpha1, 9.2.0.Final
>
>
> Stacktrace
> {code}
> java.lang.AssertionError: expected:<10> but was:<9>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.test.hibernate.cache.functional.BulkOperationsTest.testBulkOperations(BulkOperationsTest.java:97)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-8338:
-------------------------------------
[~wburns] Is this just for @Start? I think this would be nice for @PostStart and @Stop too.
> Cache start methods should run privileged
> -----------------------------------------
>
> Key: ISPN-8338
> URL: https://issues.jboss.org/browse/ISPN-8338
> Project: Infinispan
> Issue Type: Task
> Components: Security
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 9.2.0.Alpha2
>
>
> When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months