[
https://issues.apache.org/jira/browse/SLING-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4092:
-----------------------------------
Description:
While working with a large content project and working with the content
navigator contribution I started getting errors due to 'Too many open files'.
I noticed that Eclipse was hitting the 4096 open files limit. Besides the usual
suspects - jars and git pack files, I had around 600 open FileVault
serialization files.
{code}lsof -p $PID | awk '{ if ( $9 ~ /jcr_root/ ) print $9}' {code}
My first suspicion would be that the Content Navigator extension keeps the file
handles open for some reason. If this would be related to content publish, it
would also keep other files in memory, which is not the case.
was:
While working with a large content project and working with the content
navigator contribution I started getting errors due to 'Too many open files'.
I noticed that Eclipse was hitting the 4096 open files limit. Besides the usual
suspects - jars and git pack files, I had around 600 open FileVault
serialization files.
{code:bash}lsof -p $PID | awk '{ if ( $9 ~ /jcr_root/ ) print $9}' {code}
My first suspicion would be that the Content Navigator extension keeps the file
handles open for some reason. If this would be related to content publish, it
would also keep other files in memory, which is not the case.
> Eclipse run out of file descriptors due to vault files being kept open
> ----------------------------------------------------------------------
>
> Key: SLING-4092
> URL: https://issues.apache.org/jira/browse/SLING-4092
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.4
> Reporter: Robert Munteanu
> Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.6
>
>
> While working with a large content project and working with the content
> navigator contribution I started getting errors due to 'Too many open files'.
> I noticed that Eclipse was hitting the 4096 open files limit. Besides the
> usual suspects - jars and git pack files, I had around 600 open FileVault
> serialization files.
> {code}lsof -p $PID | awk '{ if ( $9 ~ /jcr_root/ ) print $9}' {code}
> My first suspicion would be that the Content Navigator extension keeps the
> file handles open for some reason. If this would be related to content
> publish, it would also keep other files in memory, which is not the case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
