You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Andrzej Bialecki (Commented) (JIRA)" <ji...@apache.org> on 2012/03/02 11:07:59 UTC

[jira] [Commented] (TIKA-863) MailContentHandler should not create AutoDetectParser on each call

    [ https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220812#comment-13220812 ] 

Andrzej Bialecki  commented on TIKA-863:
----------------------------------------

Nick, is there a chance of this making 1.1 ? Should I prepare another patch? though IIRC Jukka has changed in the meantime the way TikaConfig is inited...
                
> MailContentHandler should not create AutoDetectParser on each call
> ------------------------------------------------------------------
>
>                 Key: TIKA-863
>                 URL: https://issues.apache.org/jira/browse/TIKA-863
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.1
>            Reporter: Andrzej Bialecki 
>         Attachments: TIKA-863.patch
>
>
> MailContentHandler is called from RFC822Parser, and it creates AutoDetectParser on each call to parse(...). The process of creating AutoDetectParser involves reading TikaConfig (not cached), which in turn involves parsing XML config files. Apart from the fact that this process is wasteful and heavy, in addition in a highly concurrent setup it leads to multiple threads blocking on SAX parser creation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira