[JBoss JIRA] (ISPN-10645) Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
by Wolf-Dieter Fink (Jira)
[ https://issues.jboss.org/browse/ISPN-10645?page=com.atlassian.jira.plugin... ]
Wolf-Dieter Fink updated ISPN-10645:
------------------------------------
Status: Open (was: New)
> Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10645
> URL: https://issues.jboss.org/browse/ISPN-10645
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.CR2
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Major
>
> If a cache is populated and configured with eviction and maybe expiration the eviction will start earlier than expected and the size count will go down to more or less 0.
> Assume the cache is configured like this
> <distributed-cache name="ExpirationCache">
> <memory>
> <binary eviction="COUNT" size="120"/>
> </memory>
> <expiration lifespan="60000" interval="-1"/>
> </distributed-cache>
> The client is simple and add a new entry every second to keep the monitoring simple
> minute 1 - entries are added up to ~59 without eviction
> minute 2 - entries are added but the cache.size() is still 59
> CLI check attribute number_of_entries and evictions for the cache
> shows the same size and no eviction
> minute 3 - continue adding, cache.size()==59 but
> CLI shows the same size and increasing evictions
> minute 4 - still adding but size() decrease as well as CLI n-o-e and evictions grow
> The fact is that having less than 120 entries in the cache is unexpected as well as remove more entries after a time.
> The issue remain for
> <off-heap> and <object> with object count.
> as well as without exiration element or configured with interval - here the entries are expiring but eviction will have effects as well and drop the cache content unexpected.
> So it seems not releated to expiration at all
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10647) Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created ISPN-10647:
---------------------------------------
Summary: Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
Key: ISPN-10647
URL: https://issues.jboss.org/browse/ISPN-10647
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 10.0.0.CR2
Reporter: Wolf-Dieter Fink
Assignee: Will Burns
If a cache is populated and configured with eviction and maybe expiration the eviction will start earlier than expected and the size count will go down to more or less 0.
Assume the cache is configured like this
<distributed-cache name="ExpirationCache">
<memory>
<binary eviction="COUNT" size="120"/>
</memory>
<expiration lifespan="60000" interval="-1"/>
</distributed-cache>
The client is simple and add a new entry every second to keep the monitoring simple
minute 1 - entries are added up to ~59 without eviction
minute 2 - entries are added but the cache.size() is still 59
CLI check attribute number_of_entries and evictions for the cache
shows the same size and no eviction
minute 3 - continue adding, cache.size()==59 but
CLI shows the same size and increasing evictions
minute 4 - still adding but size() decrease as well as CLI n-o-e and evictions grow
The fact is that having less than 120 entries in the cache is unexpected as well as remove more entries after a time.
The issue remain for
<off-heap> and <object> with object count.
as well as without exiration element or configured with interval - here the entries are expiring but eviction will have effects as well and drop the cache content unexpected.
So it seems not releated to expiration at all
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10646) Custom jars in server/lib is not working
by Gustavo Lira e Silva (Jira)
[ https://issues.jboss.org/browse/ISPN-10646?page=com.atlassian.jira.plugin... ]
Gustavo Lira e Silva updated ISPN-10646:
----------------------------------------
Steps to Reproduce:
Clone https://github.com/gustavolira/ispn-10646.git or download ispn-10646.zip
Copy h2-1.4.199.jar to ${INFINISPAN_HOME}/server/lib
Start infinispan server
Run ISPN10646.java
> Custom jars in server/lib is not working
> -----------------------------------------
>
> Key: ISPN-10646
> URL: https://issues.jboss.org/browse/ISPN-10646
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR2
> Reporter: Gustavo Lira e Silva
> Priority: Major
> Attachments: h2-1.4.199.jar, ispn-10646.zip
>
>
> Custom jars added to the server classpath using server/lib folder are not working properly
> Example:
> {code:java}
> GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default");
> ConfigurationBuilder builder = new ConfigurationBuilder();
> Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class)
> .table()
> .dropOnExit(true)
> .createOnStart(true)
> .tableNamePrefix("ISPN_STRING_TABLE")
> .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
> .connectionPool()
> .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1")
> .username("sa")
> .password("sa")
> .driverClass("org.h2.Driver")
> .build();
> DefaultCacheManager cacheManager = new DefaultCacheManager(globalConfigurationBuilder.build(), build, true);
> Cache<String, String> cache = cacheManager.getCache();
> cache.put("k1", "v1");
> System.out.println(cache.get("k1"));
> {code}
> If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive {{ClassNotFoundException: org.h2.Driver}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10646) Custom jars in server/lib is not working
by Gustavo Lira e Silva (Jira)
[ https://issues.jboss.org/browse/ISPN-10646?page=com.atlassian.jira.plugin... ]
Gustavo Lira e Silva updated ISPN-10646:
----------------------------------------
Attachment: h2-1.4.199.jar
> Custom jars in server/lib is not working
> -----------------------------------------
>
> Key: ISPN-10646
> URL: https://issues.jboss.org/browse/ISPN-10646
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR2
> Reporter: Gustavo Lira e Silva
> Priority: Major
> Attachments: h2-1.4.199.jar, ispn-10646.zip
>
>
> Custom jars added to the server classpath using server/lib folder are not working properly
> Example:
> {code:java}
> GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default");
> ConfigurationBuilder builder = new ConfigurationBuilder();
> Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class)
> .table()
> .dropOnExit(true)
> .createOnStart(true)
> .tableNamePrefix("ISPN_STRING_TABLE")
> .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
> .connectionPool()
> .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1")
> .username("sa")
> .password("sa")
> .driverClass("org.h2.Driver")
> .build();
> DefaultCacheManager cacheManager = new DefaultCacheManager(globalConfigurationBuilder.build(), build, true);
> Cache<String, String> cache = cacheManager.getCache();
> cache.put("k1", "v1");
> System.out.println(cache.get("k1"));
> {code}
> If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive {{ClassNotFoundException: org.h2.Driver}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10646) Custom jars in server/lib is not working
by Gustavo Lira e Silva (Jira)
[ https://issues.jboss.org/browse/ISPN-10646?page=com.atlassian.jira.plugin... ]
Gustavo Lira e Silva updated ISPN-10646:
----------------------------------------
Attachment: ispn-10646.zip
> Custom jars in server/lib is not working
> -----------------------------------------
>
> Key: ISPN-10646
> URL: https://issues.jboss.org/browse/ISPN-10646
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.CR2
> Reporter: Gustavo Lira e Silva
> Priority: Major
> Attachments: ispn-10646.zip
>
>
> Custom jars added to the server classpath using server/lib folder are not working properly
> Example:
> {code:java}
> GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default");
> ConfigurationBuilder builder = new ConfigurationBuilder();
> Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class)
> .table()
> .dropOnExit(true)
> .createOnStart(true)
> .tableNamePrefix("ISPN_STRING_TABLE")
> .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
> .connectionPool()
> .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1")
> .username("sa")
> .password("sa")
> .driverClass("org.h2.Driver")
> .build();
> DefaultCacheManager cacheManager = new DefaultCacheManager(globalConfigurationBuilder.build(), build, true);
> Cache<String, String> cache = cacheManager.getCache();
> cache.put("k1", "v1");
> System.out.println(cache.get("k1"));
> {code}
> If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive {{ClassNotFoundException: org.h2.Driver}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10646) Custom jars in server/lib is not working
by Gustavo Lira e Silva (Jira)
Gustavo Lira e Silva created ISPN-10646:
-------------------------------------------
Summary: Custom jars in server/lib is not working
Key: ISPN-10646
URL: https://issues.jboss.org/browse/ISPN-10646
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 10.0.0.CR2
Reporter: Gustavo Lira e Silva
Custom jars added to the server classpath using server/lib folder are not working properly
Example:
{code:java}
GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default");
ConfigurationBuilder builder = new ConfigurationBuilder();
Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class)
.table()
.dropOnExit(true)
.createOnStart(true)
.tableNamePrefix("ISPN_STRING_TABLE")
.idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)")
.dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)")
.timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT")
.connectionPool()
.connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1")
.username("sa")
.password("sa")
.driverClass("org.h2.Driver")
.build();
DefaultCacheManager cacheManager = new DefaultCacheManager(globalConfigurationBuilder.build(), build, true);
Cache<String, String> cache = cacheManager.getCache();
cache.put("k1", "v1");
System.out.println(cache.get("k1"));
{code}
If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive {{ClassNotFoundException: org.h2.Driver}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10645) Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
by Wolf-Dieter Fink (Jira)
[ https://issues.jboss.org/browse/ISPN-10645?page=com.atlassian.jira.plugin... ]
Wolf-Dieter Fink reassigned ISPN-10645:
---------------------------------------
Assignee: Will Burns
> Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10645
> URL: https://issues.jboss.org/browse/ISPN-10645
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.CR2
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Major
>
> If a cache is populated and configured with eviction and maybe expiration the eviction will start earlier than expected and the size count will go down to more or less 0.
> Assume the cache is configured like this
> <distributed-cache name="ExpirationCache">
> <memory>
> <binary eviction="COUNT" size="120"/>
> </memory>
> <expiration lifespan="60000" interval="-1"/>
> </distributed-cache>
> The client is simple and add a new entry every second to keep the monitoring simple
> minute 1 - entries are added up to ~59 without eviction
> minute 2 - entries are added but the cache.size() is still 59
> CLI check attribute number_of_entries and evictions for the cache
> shows the same size and no eviction
> minute 3 - continue adding, cache.size()==59 but
> CLI shows the same size and increasing evictions
> minute 4 - still adding but size() decrease as well as CLI n-o-e and evictions grow
> The fact is that having less than 120 entries in the cache is unexpected as well as remove more entries after a time.
> The issue remain for
> <off-heap> and <object> with object count.
> as well as without exiration element or configured with interval - here the entries are expiring but eviction will have effects as well and drop the cache content unexpected.
> So it seems not releated to expiration at all
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10645) Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created ISPN-10645:
---------------------------------------
Summary: Configured eviction bases on COUNT will unexpected start eviction to early and might evict until the cache is empty
Key: ISPN-10645
URL: https://issues.jboss.org/browse/ISPN-10645
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 10.0.0.CR2
Reporter: Wolf-Dieter Fink
If a cache is populated and configured with eviction and maybe expiration the eviction will start earlier than expected and the size count will go down to more or less 0.
Assume the cache is configured like this
<distributed-cache name="ExpirationCache">
<memory>
<binary eviction="COUNT" size="120"/>
</memory>
<expiration lifespan="60000" interval="-1"/>
</distributed-cache>
The client is simple and add a new entry every second to keep the monitoring simple
minute 1 - entries are added up to ~59 without eviction
minute 2 - entries are added but the cache.size() is still 59
CLI check attribute number_of_entries and evictions for the cache
shows the same size and no eviction
minute 3 - continue adding, cache.size()==59 but
CLI shows the same size and increasing evictions
minute 4 - still adding but size() decrease as well as CLI n-o-e and evictions grow
The fact is that having less than 120 entries in the cache is unexpected as well as remove more entries after a time.
The issue remain for
<off-heap> and <object> with object count.
as well as without exiration element or configured with interval - here the entries are expiring but eviction will have effects as well and drop the cache content unexpected.
So it seems not releated to expiration at all
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (ISPN-10640) Expiration creation/lastUsed timestamp are lost when preloading from store
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10640?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10640:
------------------------------
Summary: Expiration creation/lastUsed timestamp are lost when preloading from store (was: If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence)
> Expiration creation/lastUsed timestamp are lost when preloading from store
> --------------------------------------------------------------------------
>
> Key: ISPN-10640
> URL: https://issues.jboss.org/browse/ISPN-10640
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.4.16.Final
> Environment: Cache configuration with preload
> <local-cache name="default">
> <persistence>
> <file-store shared="false" preload="true" fetch-state="true"/>
> </persistence>
> </local-cache>
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Critical
>
> If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration.
> This works correct if the server is not restarted or preload=false for the store.
> If preload is enabled and the server preload the date the creationTime is set to the current server start time.
> In this case all expiration for existing entries is not working correctly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months