[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ]
Will Burns reopened ISPN-9082:
------------------------------
> 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, 10.1.4.Final
>
>
> 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)
6 years
[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-9082:
-----------------------------
Fix Version/s: 10.1.4.Final
> 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, 10.1.4.Final
>
>
> 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)
6 years
[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ]
Will Burns resolved ISPN-9082.
------------------------------
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: 10.1.4.Final, 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)
6 years
[JBoss JIRA] (ISPN-11451) Add postgresqlplus to TableManagerFactory#guessDialect
by Gustavo Lira e Silva (Jira)
Gustavo Lira e Silva created ISPN-11451:
-------------------------------------------
Summary: Add postgresqlplus to TableManagerFactory#guessDialect
Key: ISPN-11451
URL: https://issues.redhat.com/browse/ISPN-11451
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 11.0.0.Alpha2
Reporter: Gustavo Lira e Silva
Assignee: Gustavo Lira e Silva
Postgresqlplus use a connection url like {{jdbc:edb://localhost:5444/dbname}} differently from postgres which use {{jdbc:postgresql://localhost:5432/dbname}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years