[JBoss JIRA] (ISPN-4886) SingleNodeJdbcStoreIT.testForcedShutdown and testNormalShutdown random failures
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4886?page=com.atlassian.jira.plugin.... ]
William Burns edited comment on ISPN-4886 at 10/31/14 7:53 AM:
---------------------------------------------------------------
-I was able to reproduce this for a while, but after trying to debug it was fixed and now I can no longer reproduce the failure.- From the tests it appears the value was evicted properly but wasn't then retrieved correctly, I am not sure.
*edit* I was not able to reproduce it was just because I thought the test was working a different way
was (Author: william.burns):
I was able to reproduce this for a while, but after trying to debug it was fixed and now I can no longer reproduce the failure. From the tests it appears the value was evicted properly but wasn't then retrieved correctly, I am not sure.
> SingleNodeJdbcStoreIT.testForcedShutdown and testNormalShutdown random failures
> -------------------------------------------------------------------------------
>
> Key: ISPN-4886
> URL: https://issues.jboss.org/browse/ISPN-4886
> Project: Infinispan
> Issue Type: Bug
> Components: Integration , Test Suite - Server
> Affects Versions: 7.0.0.CR2
> Reporter: Dan Berindei
> Assignee: William Burns
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.0.0.Final
>
>
> {noformat}
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at org.junit.Assert.assertNotNull(Assert.java:631)
> at org.infinispan.server.test.cs.jdbc.SingleNodeJdbcStoreIT.testRestartStringStoreBefore(SingleNodeJdbcStoreIT.java:227)
> at org.infinispan.server.test.cs.jdbc.SingleNodeJdbcStoreIT.testForcedShutdown(SingleNodeJdbcStoreIT.java:167)
> {noformat}
> Started failing again in http://ci.infinispan.org/viewLog.html?buildId=13477&buildTypeId=Infinispa...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4917) HR server authorization doesn't work
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4917?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4917:
----------------------------------
Status: Open (was: New)
> HR server authorization doesn't work
> ------------------------------------
>
> Key: ISPN-4917
> URL: https://issues.jboss.org/browse/ISPN-4917
> Project: Infinispan
> Issue Type: Bug
> Components: Security, Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
>
> HR authorization seems to be broken and allows anybody do anything, e.g. {{HotRodPlainAuthIT}} fails with
> {noformat}
> Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.87 sec <<< FAILURE! - in org.infinispan.server.test.client.hotrod.security.HotRodPlainAuthIT
> testReaderWrite(org.infinispan.server.test.client.hotrod.security.HotRodPlainAuthIT) Time elapsed: 0.081 sec <<< FAILURE!
> java.lang.AssertionError: Expected exception: org.infinispan.client.hotrod.exceptions.HotRodClientException
> at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4919) Configuration templates
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.... ]
Ion Savin commented on ISPN-4919:
---------------------------------
I think a mix of the two would make it easier to read the config: using <local-cache-template/> (no confusion about the cache not being instantiated because of the abstract flag) and referring from <local-cache/> to the template (looking at the local-cache element it's clear that additional configuration elements could be inherited, no need to look at the local-cache-templates).
> Configuration templates
> -----------------------
>
> Key: ISPN-4919
> URL: https://issues.jboss.org/browse/ISPN-4919
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Alpha1
>
>
> Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
> We should introduce the concept of configuration inheritance, e.g.:
> <local-cache name="eviction-cache">
> <eviction strategy="LIRS" maxEntries="10000"/>
> </local-cache>
> <local-cache name="mycache" template="eviction-cache" />
> Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
> <local-cache name="eviction-cache" abstract="true">
> ...
> </local-cache>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4919) Configuration templates
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4919?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-4919:
------------------------------------
I would try to go even further, and make the configuration template more prominent. Something like this:
{code}
<local-cache-template name="eviction-template" caches="mycache ...">
<eviction strategy="LIRS" max-entries="10000"/>
</local-cache-template>
{code}
> Configuration templates
> -----------------------
>
> Key: ISPN-4919
> URL: https://issues.jboss.org/browse/ISPN-4919
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Alpha1
>
>
> Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
> We should introduce the concept of configuration inheritance, e.g.:
> <local-cache name="eviction-cache">
> <eviction strategy="LIRS" maxEntries="10000"/>
> </local-cache>
> <local-cache name="mycache" template="eviction-cache" />
> Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
> <local-cache name="eviction-cache" abstract="true">
> ...
> </local-cache>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4919) Configuration templates
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-4919:
-------------------------------------
Summary: Configuration templates
Key: ISPN-4919
URL: https://issues.jboss.org/browse/ISPN-4919
Project: Infinispan
Issue Type: Feature Request
Components: Configuration
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.1.0.Alpha1
Currently there is a 1:1 relationship between configuration and named caches. While the programmatic API does have the ability to .read() an existing configuration to create a new one, the declarative config does not.
We should introduce the concept of configuration inheritance, e.g.:
<local-cache name="eviction-cache">
<eviction strategy="LIRS" maxEntries="10000"/>
</local-cache>
<local-cache name="mycache" template="eviction-cache" />
Possibly, cache templates should be made "abstract" so that they cannot be instantiated as named caches directly, e.g.:
<local-cache name="eviction-cache" abstract="true">
...
</local-cache>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4917) HR server authorization doesn't work
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-4917:
-------------------------------------
Summary: HR server authorization doesn't work
Key: ISPN-4917
URL: https://issues.jboss.org/browse/ISPN-4917
Project: Infinispan
Issue Type: Bug
Components: Security, Server
Reporter: Vojtech Juranek
Assignee: Tristan Tarrant
HR authorization seems to be broken and allows anybody do anything, e.g. {{HotRodPlainAuthIT}} fails with
{noformat}
Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.87 sec <<< FAILURE! - in org.infinispan.server.test.client.hotrod.security.HotRodPlainAuthIT
testReaderWrite(org.infinispan.server.test.client.hotrod.security.HotRodPlainAuthIT) Time elapsed: 0.081 sec <<< FAILURE!
java.lang.AssertionError: Expected exception: org.infinispan.client.hotrod.exceptions.HotRodClientException
at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months