[JBoss JIRA] (HRJS-74) Random expiry test failure
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-74?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-74:
---------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Random expiry test failure
> --------------------------
>
> Key: HRJS-74
> URL: https://issues.jboss.org/browse/HRJS-74
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 0.6.0
>
> Attachments: console_trace-HRJS-74.tgz
>
>
> {code}
> + ./node_modules/.bin/jasmine-node spec --captureExceptions --forceexit
> ......................................................................F..............................................................................
> Failures:
> 1) Infinispan local client working with expiry operations removes keys when their max idle time has expired
> Message:
> timeout: timed out after 1 msec waiting for `idle-multi1` key should be expired
> Stacktrace:
> undefined
> Finished in 89.011 seconds
> 149 tests, 603 assertions, 1 failure, 0 skipped
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9491) CacheEntryRemoved method called when Cache#remove is called even if there is no entry
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9491?page=com.atlassian.jira.plugin.... ]
William Burns resolved ISPN-9491.
---------------------------------
Resolution: Duplicate Issue
This is a duplicate of ISPN-8585
> CacheEntryRemoved method called when Cache#remove is called even if there is no entry
> -------------------------------------------------------------------------------------
>
> Key: ISPN-9491
> URL: https://issues.jboss.org/browse/ISPN-9491
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.11.Final
> Reporter: Thomas Mortagne
> Assignee: William Burns
>
> It really sounds like a bug to me to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
> The Javadoc is not super explicit about this use case but it does indicate
> {noformat}
> when a cache entry is removed from the cache
> {noformat}
> and clearly nothing was removed since nothing existed.
> By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9491) CacheEntryRemoved method called when Cache#remove is called even if there is no entry
by Thomas Mortagne (JIRA)
[ https://issues.jboss.org/browse/ISPN-9491?page=com.atlassian.jira.plugin.... ]
Thomas Mortagne updated ISPN-9491:
----------------------------------
Description:
It really sounds like a bug to me to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
The Javadoc is not super explicit about this use case but it does indicate
{noformat}
when a cache entry is removed from the cache
{noformat}
and clearly nothing was removed since nothing existed.
By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
was:
It really sounds like a bug to be to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
The Javadoc is not super explicit about this use case but it does indicate
{noformat}
when a cache entry is removed from the cache
{noformat}
and clearly nothing was removed since nothing existed.
By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
> CacheEntryRemoved method called when Cache#remove is called even if there is no entry
> -------------------------------------------------------------------------------------
>
> Key: ISPN-9491
> URL: https://issues.jboss.org/browse/ISPN-9491
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.11.Final
> Reporter: Thomas Mortagne
> Assignee: William Burns
>
> It really sounds like a bug to me to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
> The Javadoc is not super explicit about this use case but it does indicate
> {noformat}
> when a cache entry is removed from the cache
> {noformat}
> and clearly nothing was removed since nothing existed.
> By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9491) CacheEntryRemoved method called when Cache#remove is called even if there is no entry
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9491?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9491:
----------------------------------
Environment: (was: It really sounds like a bug to be to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
The Javadoc is not super explicit about this use case but it does indicate
{noformat}
when a cache entry is removed from the cache
{noformat}
and clearly nothing was removed since nothing existed.
By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.)
> CacheEntryRemoved method called when Cache#remove is called even if there is no entry
> -------------------------------------------------------------------------------------
>
> Key: ISPN-9491
> URL: https://issues.jboss.org/browse/ISPN-9491
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.11.Final
> Reporter: Thomas Mortagne
> Assignee: William Burns
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9491) CacheEntryRemoved method called when Cache#remove is called even if there is no entry
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9491?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9491:
----------------------------------
Description:
It really sounds like a bug to be to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
The Javadoc is not super explicit about this use case but it does indicate
{noformat}
when a cache entry is removed from the cache
{noformat}
and clearly nothing was removed since nothing existed.
By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
> CacheEntryRemoved method called when Cache#remove is called even if there is no entry
> -------------------------------------------------------------------------------------
>
> Key: ISPN-9491
> URL: https://issues.jboss.org/browse/ISPN-9491
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.11.Final
> Reporter: Thomas Mortagne
> Assignee: William Burns
>
> It really sounds like a bug to be to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
> The Javadoc is not super explicit about this use case but it does indicate
> {noformat}
> when a cache entry is removed from the cache
> {noformat}
> and clearly nothing was removed since nothing existed.
> By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9491) CacheEntryRemoved method called when Cache#remove is called even if there is no entry
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9491?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-9491:
-------------------------------------
Assignee: William Burns
> CacheEntryRemoved method called when Cache#remove is called even if there is no entry
> -------------------------------------------------------------------------------------
>
> Key: ISPN-9491
> URL: https://issues.jboss.org/browse/ISPN-9491
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 8.2.11.Final
> Environment: It really sounds like a bug to be to have my listener called with no value just because some code called #remove() just in case the cache contains an entry associated with the key.
> The Javadoc is not super explicit about this use case but it does indicate
> {noformat}
> when a cache entry is removed from the cache
> {noformat}
> and clearly nothing was removed since nothing existed.
> By the way this jira indicate that 8.2.11 is not released but it's available on Maven central.
> Reporter: Thomas Mortagne
> Assignee: William Burns
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months
[JBoss JIRA] (ISPN-9501) AbstractCacheStream.performOperationRehashAware() can hang
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9501?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9501:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.3.4.Final
Resolution: Done
> AbstractCacheStream.performOperationRehashAware() can hang
> ----------------------------------------------------------
>
> Key: ISPN-9501
> URL: https://issues.jboss.org/browse/ISPN-9501
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.0.CR1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final, 9.3.4.Final
>
>
> There are actually 2 different issues:
> # {{segmentsToProcess}} reuses the {{remoteResults.lostSegments}} {{ConcurrentSmallIntSet}} instance, so when {{remoteResults.lostSegments}} is cleared, {{segmentsToProcess}} is also cleared.
> # Because of ISPN-9500, {{segmentsToProcess.isEmpty()}} keeps returning {{false}}, so {{performOperationRehashAware()}} keeps waiting for a newer topology.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 7 months