[
https://issues.apache.org/jira/browse/TIKA-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490234#comment-15490234
]
Tim Barrett commented on TIKA-2058:
-----------------------------------
I'm having problems getting the patched jar into my project. I have added it to
a local repository, using:
mvn install:install-file
"-Dfile=/Users/TBarrett/Downloads/poi-3.15-beta1-p1.jar"
"-DgroupId=nalanda.downloads" "-DartifactId=org.apache.poi"
"-Dversion=3.15-beta1-p1" "-Dpackaging=jar" "-DgeneratePom=true"
"-DlocalRepositoryPath=/Users/TBarrett/Dev
Hdd/Nalanda/NalandaWorkspace/NalandaCore/lib"
and then adding it to my pom file (the pom which build my app and also has a
dependency on tika-1.13) using:
<dependency>
<groupId>nalanda.downloads</groupId>
<artifactId>org.apache.poi</artifactId>
<version>3.15-beta1-p1</version>
</dependency>
The jar is then added to my project however it then shows up as a jar file that
nothing is dependent on, whereas tika-core and tika-parsers still seem to be
dependent on the original poi jar from org.apache.poi
If you have changed only a small number of source files as part fo the patch,
if you could send me those sources I can add them directly to my project
sources which is sure to invoke the patch.
> Memory Leak in Tika version 1.13 when parsing millions of files
> ---------------------------------------------------------------
>
> Key: TIKA-2058
> URL: https://issues.apache.org/jira/browse/TIKA-2058
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.13
> Reporter: Tim Barrett
> Attachments: poi-3.15-beta1-p1.jar, screenshot-1.png,
> screenshot-2.png, screenshot-3.png
>
>
> We have an application using Tika which parses roughly 7,000,000 files of
> different types, many of the files are MSG files with attachments. This works
> correctly with Tika 1.9, and has been in production for over a year, with
> parsing runs taking place every few weeks. The same application runs into
> insufficient memory problems (java heap) when using Tika 1.13.
> I have used lsof and file leak detector to track down open files, however
> neither shows any open files when the application is running. I did find an
> issue with open files https://issues.apache.org/jira/browse/TIKA-2015,
> however there was a workaround for this and this is not the issue.
> I am sorry to have to report this with a level of vagueness, but with lsof
> turning nothing up I am a bit stuck as to how to investigate further. We are
> more than willing to help by testing on the basis of any ideas provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
