[JBoss JIRA] (HRJS-84) Implicitly close iterator when done
by Galder Zamarreño (Jira)
Galder Zamarreño created HRJS-84:
------------------------------------
Summary: Implicitly close iterator when done
Key: HRJS-84
URL: https://issues.jboss.org/browse/HRJS-84
Project: Infinispan Javascript client
Issue Type: Enhancement
Reporter: Galder Zamarreño
Client should implicitly close the iterator when the iteration is done.
Currently it requires the client to call close on the iterator to make sure it's closed server side.
This is related to ISPN-9195/ISPN-10169.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (ISPN-10170) DG HTTP Session Externalization
by Donald Naro (Jira)
Donald Naro created ISPN-10170:
----------------------------------
Summary: DG HTTP Session Externalization
Key: ISPN-10170
URL: https://issues.jboss.org/browse/ISPN-10170
Project: Infinispan
Issue Type: Enhancement
Components: Documentation-Core
Reporter: Donald Naro
Assignee: Donald Naro
Downstream documentation required for HTTP session externalization.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (ISPN-10169) Hot Rod iteration state is kept around forever if IterationEnd is not invoked
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10169?page=com.atlassian.jira.plugin... ]
Tristan Tarrant closed ISPN-10169.
----------------------------------
Resolution: Duplicate Issue
> Hot Rod iteration state is kept around forever if IterationEnd is not invoked
> -----------------------------------------------------------------------------
>
> Key: ISPN-10169
> URL: https://issues.jboss.org/browse/ISPN-10169
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, Server
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: rhdemo-2019
>
> The DefaultIterationManager keeps a map of iterationstate for each active client iteration. Unfortunately, if the client does invoke the end operation, these states can linger forever. We should:
> * reap iterationstates when the channel that created them is closed
> * reap iterationstates which have been inactive for a long time
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years
[JBoss JIRA] (ISPN-9195) Iterator leak when Hot Rod client crashes
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9195?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-9195:
-------------------------------------
Assignee: Tristan Tarrant (was: Gustavo Fernandes)
> Iterator leak when Hot Rod client crashes
> -----------------------------------------
>
> Key: ISPN-9195
> URL: https://issues.jboss.org/browse/ISPN-9195
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.3.0.Beta1
> Reporter: Radim Vansa
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: memory_leak
>
> When the client abruptly terminates, or simply does not close the iterator, iterator resources on server are not released.
> Any such resources should be handles with lease-based expiration. Additionally we could remove the resources when the connection that established them is closed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years