You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Joey Ezekiel (JIRA)" <ji...@apache.org> on 2013/05/23 14:35:20 UTC
[jira] [Updated] (FOP-2189) Apache FOP 1.0 Multithreading Problems
- Too many open files err24
[ https://issues.apache.org/jira/browse/FOP-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joey Ezekiel updated FOP-2189:
------------------------------
Priority: P1 (was: P2)
> Apache FOP 1.0 Multithreading Problems - Too many open files err24
> ------------------------------------------------------------------
>
> Key: FOP-2189
> URL: https://issues.apache.org/jira/browse/FOP-2189
> Project: Fop
> Issue Type: Bug
> Components: pdf
> Affects Versions: 1.0
> Environment: HP Unix
> Reporter: Joey Ezekiel
> Labels: Exception, Font", IOException, PDF, error
> Fix For: trunk
>
>
> We use Apache FOP to convert a whole lot of XML's to AFP's and PDF's. Our current load would be around 25k files per run on a HP-UX system. We have 12 threads in total that are used to initialize and trigger the FOP conversion in a producer-consumer fashion. Recently there have been multiple failures during conversion and when looked up, we've received generic FOP errors like:
> **ERROR,2460364,FOToPDF_Thread_11,FOP Exception, something.pdf,Failed to resolve font with embed-url './Fonts/arial.ttf'**
> or its an error failing to load the font metrics file although the files are intact with the right permissions. Many other PDF's are generated so this can't be the problem.
> We also wind up with:
> **java.io.FileNotFoundException: /PDF/20130111130002/something.pdf (Too many open files (errno:24))**
> judging by the logs and volume being processed, this looks like an FOP problem. I've read that FOP has had this issue in the past with the font files. There have been instances where Apache has opened each font file multiple times and not closed the handles resulting in a large number of open files. This was supposed to be fixed, but if it still persists, what would be a good and quick solution to this?
--
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