[ 
https://issues.apache.org/jira/browse/TEXEN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Will Glass-Husain resolved TEXEN-1.
-----------------------------------

    Resolution: Fixed

Added patch.  (though I changed the use of Hashtable to Set).  Thanks so much!

As an aside, In the future, try doing "svn diff" when contributing patches.  
It's easy to do and it puts it in standard unified format  which is easy to 
patch.

> No upper limit on cached file handles causes random ResourceLoader exceptions
> -----------------------------------------------------------------------------
>
>                 Key: TEXEN-1
>                 URL: https://issues.apache.org/jira/browse/TEXEN-1
>             Project: Texen
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ian Ragsdale
>         Attachments: breaktexen.xml, Generator.java.patch
>
>
> The Generator class caches filehandles while generating files.  There is no
> upper limit on the number of filehandles it will cache, so when generating 
> many
> files with the same generator, it eventually hits the per-process limits on 
> the
> number of open files.  This then causes failures in the resource loader 
> because
> it cannot open any more files.  I've seen this problem on OS X and Linux, but 
> it
> should be a pretty universal problem.
> You can work around this problem by increasing the number of filehandles
> available to the ant task, but that isn't always easy to do when running it 
> as a
> subtask from an IDE, and it should be fairly simple to implement a basic LRU 
> scheme.
> An alternative fix would be to more accurately report the error - the current
> implementation just throws a ResourceNotFound exception, making it very hard 
> to
> track down the root cause of the error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to