[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=13210205#comment-13210205 ] Nick Burch commented on TIKA-863: - I'm not sure if we should be setting it as AutoDetectPars

[jira] [Commented] (TIKA-864) Metadata.formatDate should use ThreadLocal

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210207#comment-13210207 ] Nick Burch commented on TIKA-864: - If we did store them on a ThreadLocal, then how would we

[jira] [Commented] (TIKA-865) MimeTypes.forName should avoid method-level synchronization

[ https://issues.apache.org/jira/browse/TIKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210209#comment-13210209 ] Nick Burch commented on TIKA-865: - I've had a go at fixing this in r1245426. It'd be good if

[jira] [Created] (TIKA-866) Incomplete configuration file causes OutOfMemoryException

Incomplete configuration file causes OutOfMemoryException - Key: TIKA-866 URL: https://issues.apache.org/jira/browse/TIKA-866 Project: Tika Issue Type: Bug Components: config

[jira] [Updated] (TIKA-866) Incomplete configuration file causes OutOfMemoryException

[ https://issues.apache.org/jira/browse/TIKA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Mühlstrasser updated TIKA-866: -- Attachment: ConfigFile.java Unit test to reproduce the problem. > Incomp

[jira] [Commented] (TIKA-866) Incomplete configuration file causes OutOfMemoryException

[ https://issues.apache.org/jira/browse/TIKA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210219#comment-13210219 ] Nick Burch commented on TIKA-866: - If the Tika Config file is missing elements (eg only has

[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=13210221#comment-13210221 ] Andrzej Bialecki commented on TIKA-863: I see your point, it makes sense - no hidde

[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=13210236#comment-13210236 ] Nick Burch commented on TIKA-863: - I'm not sure what the best way is to provide an AutoDetec

[jira] [Commented] (TIKA-865) MimeTypes.forName should avoid method-level synchronization

[ https://issues.apache.org/jira/browse/TIKA-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210237#comment-13210237 ] Jukka Zitting commented on TIKA-865: I'd keep the synchronization on "this", as it also

[jira] [Commented] (TIKA-864) Metadata.formatDate should use ThreadLocal

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210238#comment-13210238 ] Andrzej Bialecki commented on TIKA-864: Good point. Maybe Tika should use Joda-Time

[jira] [Commented] (TIKA-864) Metadata.formatDate should use ThreadLocal

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210240#comment-13210240 ] Jukka Zitting commented on TIKA-864: Like in TIKA-865, is this a real measurable perform

[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=13210242#comment-13210242 ] Andrzej Bialecki commented on TIKA-863: This would work in my case, too. Though the

Jenkins build is back to normal : Tika-trunk #800

See

[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=13210245#comment-13210245 ] Nick Burch commented on TIKA-863: - We could check for the TikaConfig on the ParseContext, wh

[jira] [Commented] (TIKA-864) Metadata.formatDate should use ThreadLocal

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210247#comment-13210247 ] Andrzej Bialecki commented on TIKA-864: I noticed this issue when profiling a large

[jira] [Updated] (TIKA-866) Invalid configuration file causes OutOfMemoryException

[ https://issues.apache.org/jira/browse/TIKA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated TIKA-866: --- Summary: Invalid configuration file causes OutOfMemoryException (was: Incomplete configuration file ca

[jira] [Resolved] (TIKA-866) Invalid configuration file causes OutOfMemoryException

[ https://issues.apache.org/jira/browse/TIKA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved TIKA-866. Resolution: Fixed Fix Version/s: 1.1 Assignee: Jukka Zitting Fixed in revision 124544

[jira] [Updated] (TIKA-864) Metadata.formatDate causes blocking in concurrent use

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated TIKA-864: --- Summary: Metadata.formatDate causes blocking in concurrent use (was: Metadata.formatDate should use Th

[jira] [Resolved] (TIKA-864) Metadata.formatDate causes blocking in concurrent use

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved TIKA-864. Resolution: Fixed Fix Version/s: 1.1 Assignee: Jukka Zitting bq. perhaps the best sol

[jira] [Issue Comment Edited] (TIKA-864) Metadata.formatDate causes blocking in concurrent use

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210313#comment-13210313 ] Jukka Zitting edited comment on TIKA-864 at 2/17/12 3:10 PM: - bq

buildbot failure in ASF Buildbot on tika-trunk

The Buildbot has detected a new failure on builder tika-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tika-trunk/builds/749 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp: [

[jira] [Commented] (TIKA-866) Invalid configuration file causes OutOfMemoryException

[ https://issues.apache.org/jira/browse/TIKA-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210429#comment-13210429 ] Jukka Zitting commented on TIKA-866: Actually, scrap the above rationale. The DefaultPar

Re: buildbot failure in ASF Buildbot on tika-trunk

Hi, On Fri, Feb 17, 2012 at 7:26 PM, wrote: > The Buildbot has detected a new failure on builder tika-trunk Sorry, my config handling change apparently broke OSGi service loading. I'll fix that later tonight. BR, Jukka Zitting

[jira] [Commented] (TIKA-864) Metadata.formatDate causes blocking in concurrent use

[ https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210694#comment-13210694 ] Andrzej Bialecki commented on TIKA-864: Thanks Jukka, this solved the issue nicely

[jira] [Commented] (TIKA-853) java.io.IOException with TikaGUI and testMP4.m4a

[ https://issues.apache.org/jira/browse/TIKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210807#comment-13210807 ] John Mastarone commented on TIKA-853: - I think I have a better fix for this that does no