[
https://issues.apache.org/jira/browse/TIKA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300966#comment-14300966
]
Andrew Hwang commented on TIKA-1537:
------------------------------------
Hi Tyler,
I had already tried setting the MAVEN_OPTS environment variable, but it
continued to fail. I did some searching around on Google, and found this from
StackOverflow:
http://stackoverflow.com/questions/4066424/java-lang-outofmemoryerror-java-heap-space-in-maven.
From what I could gather, the maven-surefire-plugin forks a new JVM and the
amount of memory set in MAVEN_OPTS is not passed onto the new JVM.
> Installation on OSX 10.10.2 generates OutOfMemory Error during parser tests
> ---------------------------------------------------------------------------
>
> Key: TIKA-1537
> URL: https://issues.apache.org/jira/browse/TIKA-1537
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.7
> Environment: Mac OSX 10.10.2
> Reporter: Andrew Hwang
> Priority: Minor
> Labels: easyfix
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I was having issues during installation of Tika 1.7 where the build failed
> when running parser tests (specifically on TestChmExtraction). I had set the
> MAVEN_OPTS variable to have enough memory (-Xmx2048m), but the build still
> failed. I turned out that the maven-surefire-plugin was creating a new JVM
> that did not have enough specified memory, causing TestChmExtraction to fail.
> A fix I found online led me to change the POM for tika-parent (adding an
> argLine to maven-surefire-plugin, where -Xmx2048m worked). After adding this,
> the installation was able to finish. I will submit a pull request with the
> addition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
