[JBoss JIRA] (ISPN-11204) Response Collector addResponse value can be ignored
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11204?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11204:
------------------------------
Description: A ResponseCollector can return a non null value from `addResponse` that is a sign that the response is complete. However it is possible to get a non null value from one response and get another response that has null and the `finish` value is used instead. We should make sure that when a non null value is returned via `addResponse` that its value is always used. (was: A ResponseCollector can return a non value from `addResponse` that is a sign that the response is complete. However it is possible to get a non null value from one response and get another response that has null and the `finish` value is used instead. We should make sure that when a non null value is returned via `addResponse` that its value is always used.)
> Response Collector addResponse value can be ignored
> ---------------------------------------------------
>
> Key: ISPN-11204
> URL: https://issues.redhat.com/browse/ISPN-11204
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Alpha1
>
>
> A ResponseCollector can return a non null value from `addResponse` that is a sign that the response is complete. However it is possible to get a non null value from one response and get another response that has null and the `finish` value is used instead. We should make sure that when a non null value is returned via `addResponse` that its value is always used.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-11204) Response Collector addResponse value can be ignored
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11204?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11204:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Response Collector addResponse value can be ignored
> ---------------------------------------------------
>
> Key: ISPN-11204
> URL: https://issues.redhat.com/browse/ISPN-11204
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Alpha1
>
>
> A ResponseCollector can return a non value from `addResponse` that is a sign that the response is complete. However it is possible to get a non null value from one response and get another response that has null and the `finish` value is used instead. We should make sure that when a non null value is returned via `addResponse` that its value is always used.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-9082:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Off Heap maxIdle expiration is not implemented
> ----------------------------------------------
>
> Key: ISPN-9082
> URL: https://issues.redhat.com/browse/ISPN-9082
> Project: Infinispan
> Issue Type: Bug
> Components: Expiration, Off Heap
> Affects Versions: 9.2.1.Final
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Alpha1
>
>
> Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months