[JBoss JIRA] (ISPN-5863) Expiration configuration in C/S mode for a cache does not work
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-5863:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1272052
Bugzilla Update: Perform
> Expiration configuration in C/S mode for a cache does not work
> --------------------------------------------------------------
>
> Key: ISPN-5863
> URL: https://issues.jboss.org/browse/ISPN-5863
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Priority: Critical
>
> If the ISPN server cache is configured with expiration like:
> <cache-container name="local" default-cache="default" statistics="true">
> <state-persistence/>
> <local-cache name="default" start="EAGER">
> <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <expiration lifespan="1000" interval="20000"/>
> </local-cache>
> The entry should automatic expired in 1second after it is added.
> But a client still have the key
> - after 1 sec where it should have been expired
> - after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5865) Missing "key-to-string-mapper" element in the cachestore jdbc config schema file
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-5865:
---------------------------------------
Summary: Missing "key-to-string-mapper" element in the cachestore jdbc config schema file
Key: ISPN-5865
URL: https://issues.jboss.org/browse/ISPN-5865
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Reporter: Gustavo Fernandes
Although the parser reads the attribute, the snippet below is technically invalid according to infinispan-cachestore-jdbc-config-8.0.xsd
{code}
<string-keyed-jdbc-store xmlns="urn:infinispan:config:store:jdbc:8.0"
key-to-string-mapper="org.infinispan.lucene.LuceneKey2StringMapper"
fetch-state="false"
read-only="false"
preload="true"
purge="true">
</string-keyed-jdbc-store>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5863) Expiration configuration in C/S mode for a cache does not work
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-5863:
--------------------------------------
Summary: Expiration configuration in C/S mode for a cache does not work
Key: ISPN-5863
URL: https://issues.jboss.org/browse/ISPN-5863
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.1.0.Alpha1
Reporter: Wolf-Dieter Fink
Priority: Critical
If the ISPN server cache is configured with expiration like:
<cache-container name="local" default-cache="default" statistics="true">
<state-persistence/>
<local-cache name="default" start="EAGER">
<locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
<transaction mode="NONE"/>
<expiration lifespan="1000" interval="20000"/>
</local-cache>
The entry should automatic expired in 1second after it is added.
But a client still have the key
- after 1 sec where it should have been expired
- after 20 sec where the reaper should have removed it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5756) Improve EmbeddedCacheManager.removeCache() method
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-5756?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reopened ISPN-5756:
-------------------------------------
Reopening, since the proposed changes in the PR causes some issues in the query module: test errors, timeout exceptions and ultimately hanging.
> Improve EmbeddedCacheManager.removeCache() method
> -------------------------------------------------
>
> Key: ISPN-5756
> URL: https://issues.jboss.org/browse/ISPN-5756
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 8.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 8.1.0.Alpha2
>
>
> We have the following issues with the method
> 1) It is not consistent in all the nodes
> 2) Removing the cache remotely and locally can be done in parallel
> 3) When passivation is enabled, it passivates the entries and then clear the cache store.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months