[JBoss JIRA] (RF-11745) OutOfMemoryError: PermGen space when building on Jenkins
by Pavol Pitonak (Created) (JIRA)
OutOfMemoryError: PermGen space when building on Jenkins
--------------------------------------------------------
Key: RF-11745
URL: https://issues.jboss.org/browse/RF-11745
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: build/distribution
Affects Versions: 4.1.0.CR1
Reporter: Pavol Pitonak
When RichFaces are built from Jenkins without any extra settings for heap and perm gen. However, it works fine if following options are set *-Xmx512m -XX:MaxPermSize=128m*. Isn't it possible to set those values directly in build (pom.xml)?
{code}
mvn -f build/pom.xml -Pbuild,release clean deploy
{code}
{quote}
[INFO] RichFaces UI Components: Drag-n-Drop Aggregator ... SUCCESS [0.129s]
[INFO] RichFaces UI Components: Validator api ............ SUCCESS [15.729s]
[INFO] RichFaces UI Components: Validator ui ............. SUCCESS [4:17.709s]
[INFO] RichFaces UI Components: validator-aggregator ..... SUCCESS [0.186s]
[INFO] Richfaces UI Components API ....................... SUCCESS [1:22.666s]
[INFO] RichFaces UI Components Static Resources .......... SUCCESS [2:08.555s]
[INFO] RichFaces UI Components UI ........................ SUCCESS [2:56.547s]
[INFO] RichFaces UI Distribution ......................... SUCCESS [0.099s]
[INFO] RichFaces UI Components Aggregator ................ SUCCESS [0.099s]
[INFO] RichFaces Showcase ................................ FAILURE [1:57.991s]
[INFO] RichFaces Distribution Assembler .................. SKIPPED
[INFO] RichFaces Aggregator .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 57:50.540s
[INFO] Finished at: Mon Nov 28 05:38:15 EST 2011
[INFO] Final Memory: 123M/577M
[INFO] ------------------------------------------------------------------------
---------------------------------------------------
constituent[0]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-embedder-3.0.3.jar
constituent[1]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-3.0.3.jar
constituent[2]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-utils-2.0.6.jar
constituent[3]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-core-3.0.3.jar
constituent[4]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-3.0.3.jar
constituent[5]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-settings-builder-3.0.3.jar
constituent[6]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-interpolation-1.14.jar
constituent[7]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-component-annotations-1.5.5.jar
constituent[8]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-sec-dispatcher-1.3.jar
constituent[9]: file:/qa/tools/opt/apache-maven-3.0.3/lib/plexus-cipher-1.4.jar
constituent[10]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-repository-metadata-3.0.3.jar
constituent[11]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-artifact-3.0.3.jar
constituent[12]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-plugin-api-3.0.3.jar
constituent[13]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-plexus-2.1.1.jar
constituent[14]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-inject-bean-2.1.1.jar
constituent[15]: file:/qa/tools/opt/apache-maven-3.0.3/lib/sisu-guice-2.9.4-no_aop.jar
constituent[16]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-model-builder-3.0.3.jar
constituent[17]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-aether-provider-3.0.3.jar
constituent[18]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-api-1.11.jar
constituent[19]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-spi-1.11.jar
constituent[20]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-util-1.11.jar
constituent[21]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-impl-1.11.jar
constituent[22]: file:/qa/tools/opt/apache-maven-3.0.3/lib/maven-compat-3.0.3.jar
constituent[23]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-provider-api-1.0-beta-7.jar
constituent[24]: file:/qa/tools/opt/apache-maven-3.0.3/lib/commons-cli-1.2.jar
constituent[25]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-lightweight-1.0-beta-7.jar
constituent[26]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-http-shared-1.0-beta-7.jar
constituent[27]: file:/qa/tools/opt/apache-maven-3.0.3/lib/xercesMinimal-1.9.6.2.jar
constituent[28]: file:/qa/tools/opt/apache-maven-3.0.3/lib/nekohtml-1.9.6.2.jar
constituent[29]: file:/qa/tools/opt/apache-maven-3.0.3/lib/wagon-file-1.0-beta-7.jar
constituent[30]: file:/qa/tools/opt/apache-maven-3.0.3/lib/aether-connector-wagon-1.11.jar
---------------------------------------------------
Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
Exception in thread "Thread-1200" java.lang.OutOfMemoryError: PermGen space
Archiving artifacts
Finished: FAILURE
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (RF-11810) Fix the richfaces-components-ui build to do not overwrite assemblied JAR
by Lukáš Fryč (Created) (JIRA)
Fix the richfaces-components-ui build to do not overwrite assemblied JAR
------------------------------------------------------------------------
Key: RF-11810
URL: https://issues.jboss.org/browse/RF-11810
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: build/distribution
Affects Versions: 4.1.0.Final
Reporter: Marek Novotny
(Issue reported by Lukas Fryc)
Marek Novotny (manaRH) has recently reported that sometimes RF build fails for him since {{richfaces-components-ui}} module is generating JAR using {{maven-assembly-plugin}} which has the same name as the standard {{maven-jar-plugin}} artifact would be called.
The symptoms are failing applications (and functional tests) which are not able to use any UI implementation classes.
This may lead into potential clash for bad timings, especially when these plugins are ran on the same lifecycle phase.
We should either:
# change lifecycle mapping of plugins
# modify {{maven-jar-plugin}} settings
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months