| Summary: | maven fails to execute on Power | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Amir Sanjar <v1sanjar> |
| Component: | java-1.7.0-openjdk | Assignee: | jiri vanek <jvanek> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | ahughes, akurtako, dbhole, java-sig-commits, jerboaa, jvanek, mizdebsk, msrb, omajid, sochotni |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | ppc64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-08 12:14:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1015432 | ||
| Bug Blocks: | |||
I believe this has been identified before as OpenJDK bug. Reassigning to appropriate component Again this problem is only reproducible on POWER, it works fine on x86. As you can see (below) both x86 and POWER have the same OpenJDK version. *** POWER **** [mockbuild@p20n09 ~]$ java -version java version "1.7.0_40" OpenJDK Runtime Environment (fedora-2.4.2.9.fc20-ppc64 u40-b60) OpenJDK 64-Bit Zero VM (build 24.0-b56, interpreted mode) *** X86 ***** [mockbuild@localhost rpmbuild]$ java -version java version "1.7.0_40" OpenJDK Runtime Environment (fedora-2.4.2.9.fc20-x86_64 u40-b60) OpenJDK 64-Bit Server VM (build 24.0-b56, mixed mode) This looks identical to an issue Chris is already looking into. Re-assigning to him. *** This bug has been marked as a duplicate of bug 1015432 *** Not just PPC, but PPC where -XX:+UseLargePages is enabled with hugetlb as far as we can tell. OpenJDK reads the value of Hugepagesize from /proc/meminfo and this has been observed as being as large as 16MB on some PPC boxes. Bug 1015432 is closed for public access. This bugs needs to remain open for Fedora tracking. Adding it as a dependency for tracking purposes though. any updates? Hi The work-around for https://bugzilla.redhat.com/show_bug.cgi?id=1015432 should fix the stack overflow but it requires a new openjdk build, you may also have to increase perm gen if you see the oom permgen msg https://bugzilla.redhat.com/show_bug.cgi?id=1017606 Chris Odd ??!! I get error "You are not authorized to access bug #1015432. " By the way, Scala console also failing on Power the same way. Jiri, can you please do a Fedora build with the PPC stackoverflow fix? The stackowerflow fix was pushed and built. |
Description of problem: maven fails to execute. Version-Release number of selected component (if applicable): [mockbuild@p20n09 ~]$ mvn -v Apache Maven 3.1.0 (NON-CANONICAL_2013-09-26_13-27_mockbuild; 2013-09-26 07:27:45-0600) Maven home: /usr/share/maven Java version: 1.7.0_40, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.ppc64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.11.0-300.fc20.ppc64p7", arch: "ppc64", family: "unix" How reproducible: just type "mvn" Steps to Reproduce: 1.yum instsall maven 2.type "mvn" 3. Actual results: Exception in thread "process reaper" Exception in thread "process reaper" java.lang.StackOverflowError at java.lang.UNIXProcess$ProcessPipeInputStream.processExited(UNIXProcess.java:282) at java.lang.UNIXProcess.processExited(UNIXProcess.java:187) at java.lang.UNIXProcess$3.run(UNIXProcess.java:175) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Exception in thread "process reaper" Exception in thread "process reaper" Exception in thread "process reaper" Exception in thread "process reaper" java.lang.StackOverflowError at java.util.concurrent.SynchronousQueue$TransferStack.snode(SynchronousQueue.java:316) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:358) at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Expected results: [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.076s [INFO] Finished at: Fri Oct 25 09:43:42 CDT 2013 [INFO] Final Memory: 4M/119M [INFO] ------------------------------------------------------------------------ [ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-site, site, post-site, site-deploy, pre-clean, clean, post-clean. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException Additional info: