[
https://issues.apache.org/jira/browse/TIKA-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210236#comment-13210236
]
Nick Burch commented on TIKA-863:
---------------------------------
I'm not sure what the best way is to provide an AutoDetectParser for this case
though.
MailContentHandler does seem to me to behave differently to cases like Zip,
which have multiple sub-parts, and it is different to cases like word-with-excel
Maybe we should check for an AutoDetectParser on the context, use that if
given, and if not lazy-create + cache a default one on the parser, and supply
that through to the mail content handler?
> 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
