[
https://issues.jboss.org/browse/ISPN-2874?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-2874:
---------------------------------------
The problem is that the default fetch mode for results implementing the java.lang.Iterable
was changed to LAZY fetch mode.
This mode isn't exactly Iterable but its extension org.infinispan.query.ResultIterator
: the main but very important difference is that such an Iterator has a close() method
which needs to be invoked to avoid such resource leaks.
Bottomline, having the default as LAZY isn't suited for usage in "enhanced for
loops" as the API user doesn't realize the mistake - and has no option to fix it
anyway.
Workaround: avoid enhanced for loops to iterate on the resultsets.
Index File handles leak
-----------------------
Key: ISPN-2874
URL:
https://issues.jboss.org/browse/ISPN-2874
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.2.0.Final, 5.2.1.Final, 5.2.2.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 5.2.3.Final, 5.3.0.Alpha1
This forum post seems reliable and needs urgent investigation:
https://community.jboss.org/thread/221319
Seems that Infinispan Query is leaking references to open index readers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira