You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/08/08 05:29:27 UTC
[jira] [Created] (FELIX-3071) [Framework] It should be possible to
limit number of open JAR files
[Framework] It should be possible to limit number of open JAR files
-------------------------------------------------------------------
Key: FELIX-3071
URL: https://issues.apache.org/jira/browse/FELIX-3071
Project: Felix
Issue Type: Improvement
Components: Framework
Affects Versions: framework-3.2.2
Reporter: Richard S. Hall
Assignee: Richard S. Hall
Fix For: framework-4.0.0
Currently, the framework opens a ZipFile for each bundle JAR file and one for each embedded JAR file on a bundle's class path. Needless to say, if you have lots of bundles in your system, this can lead to lots of open files for the framework process. It should be possible to modify the framework to obey some limit on the number of open ZipFiles.
A general approach would be to have a configurable limit and whenever the framework wanted to open another, if the limit was exceeded it would have to close a not recently used ZipFile. Theoretically, this shouldn't be too much of an issue for classes in particular, because once they are loaded they are cached in memory and it isn't necessary to go back to the disk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3071) [Framework] It should be possible
to limit number of open JAR files
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091317#comment-13091317 ]
Richard S. Hall commented on FELIX-3071:
----------------------------------------
I've implemented this, but I'm going to leave this issue open to see if we run into any issues.
> [Framework] It should be possible to limit number of open JAR files
> -------------------------------------------------------------------
>
> Key: FELIX-3071
> URL: https://issues.apache.org/jira/browse/FELIX-3071
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-3.2.2
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-4.0.0
>
>
> Currently, the framework opens a ZipFile for each bundle JAR file and one for each embedded JAR file on a bundle's class path. Needless to say, if you have lots of bundles in your system, this can lead to lots of open files for the framework process. It should be possible to modify the framework to obey some limit on the number of open ZipFiles.
> A general approach would be to have a configurable limit and whenever the framework wanted to open another, if the limit was exceeded it would have to close a not recently used ZipFile. Theoretically, this shouldn't be too much of an issue for classes in particular, because once they are loaded they are cached in memory and it isn't necessary to go back to the disk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3071) [Framework] It should be possible
to limit number of open JAR files
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091320#comment-13091320 ]
Richard S. Hall commented on FELIX-3071:
----------------------------------------
Reminder to myself, I've set the default limit to an artificially low limit right now (10 open files) to try to force any issues to be visible. Before closing this issue, I'll set the default limit to 0 (i.e., unlimited).
> [Framework] It should be possible to limit number of open JAR files
> -------------------------------------------------------------------
>
> Key: FELIX-3071
> URL: https://issues.apache.org/jira/browse/FELIX-3071
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-3.2.2
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-4.0.0
>
>
> Currently, the framework opens a ZipFile for each bundle JAR file and one for each embedded JAR file on a bundle's class path. Needless to say, if you have lots of bundles in your system, this can lead to lots of open files for the framework process. It should be possible to modify the framework to obey some limit on the number of open ZipFiles.
> A general approach would be to have a configurable limit and whenever the framework wanted to open another, if the limit was exceeded it would have to close a not recently used ZipFile. Theoretically, this shouldn't be too much of an issue for classes in particular, because once they are loaded they are cached in memory and it isn't necessary to go back to the disk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3071) [Framework] It should be possible to
limit number of open JAR files
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-3071.
----------------------------------
Resolution: Fixed
Set default limit to be unlimited. Closing.
> [Framework] It should be possible to limit number of open JAR files
> -------------------------------------------------------------------
>
> Key: FELIX-3071
> URL: https://issues.apache.org/jira/browse/FELIX-3071
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-3.2.2
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-4.0.0
>
>
> Currently, the framework opens a ZipFile for each bundle JAR file and one for each embedded JAR file on a bundle's class path. Needless to say, if you have lots of bundles in your system, this can lead to lots of open files for the framework process. It should be possible to modify the framework to obey some limit on the number of open ZipFiles.
> A general approach would be to have a configurable limit and whenever the framework wanted to open another, if the limit was exceeded it would have to close a not recently used ZipFile. Theoretically, this shouldn't be too much of an issue for classes in particular, because once they are loaded they are cached in memory and it isn't necessary to go back to the disk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira