[
https://issues.apache.org/jira/browse/JCR-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985577#action_12985577
]
Sébastien Launay commented on JCR-2864:
---------------------------------------
I like this isolation because we can also kill parsers blocked into a infinite
loop.
But there might be an issue at least on GNU/Linux systems (vanilla kernel)
because of how processes are created.
Indeed, creating a process required the same amount of free memory as the
memory consumed by the parent process (fork() then exec()).
This can be a big issue for enterprise server where a lot of memory is
dedicated to the JVM and creating subprocesses would result in the system
swapping or error like "Cannot run program "java": java.io.IOException:
error=12, Cannot allocate memory".
A solution often recommended is to start one light process parallel to the main
one and communicate with it (e.g. by socket) to create the subprocesses.
More information can be found here:
http://developers.sun.com/solaris/articles/subprocess/subprocess.html
> Use out-of-process text extraction
> ----------------------------------
>
> Key: JCR-2864
> URL: https://issues.apache.org/jira/browse/JCR-2864
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: indexing, jackrabbit-core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.3.0
>
>
> The upcoming Tika 0.9 release will contain a highly useful out-of-process
> text extraction feature (TIKA-416) that we should use also in Jackrabbit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
