tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-863) MailContentHandler should not create AutoDetectParser on each call
Date Sat, 30 Jun 2012 17:42:44 GMT

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

Nick Burch resolved TIKA-863.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.2
    
> 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 
>             Fix For: 1.2
>
>         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

        

Mime
View raw message