Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

JIra 4.4.1 build fails with "out of space in CodeCache for adapters"

Wolfgang Stichling November 22, 2011

I am attempting to build Jira 4.4.1 from source and have run into a road block. The build keeps failing here:

> [INFO] ------------------------------------------------------------------------

> [INFO] Building Atlassian JIRA - Plugins - Bundled Plugins

> [INFO] task-segment: [clean, package]

> [INFO] ------------------------------------------------------------------------

> [INFO] [clean:clean]

> [INFO] [enforcer:enforce {execution: enforce-versions}]

> [INFO] [sandbox:sandbox {execution: enable-sandbox}]

> [INFO] [yuicompressor:compress {execution: default}]

> [INFO] nb warnings: 0, nb errors: 0

> [INFO] [compiler:compile {execution: compile}]

> [INFO] No sources to compile

> [INFO] [compiler:testCompile {execution: unit-test-compile}]

> [INFO] Not compiling test sources

> [INFO] [site:attach-descriptor]

> [INFO] [smartass:archive-dependencies {execution: create-bundled-plugins-zip}]

> [INFO] ------------------------------------------------------------------------

> [ERROR] FATAL ERROR

> [INFO] ------------------------------------------------------------------------

> [INFO] out of space in CodeCache for adapters

> [INFO] ------------------------------------------------------------------------

> [INFO] Trace

> java.lang.VirtualMachineError: out of space in CodeCache for adapters

> at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor

> (AbstractCallSite.java:200)

> at com.luuuis.maven.smartass.ArchiveDependenciesMojo.execute(ArchiveDepe

> ndenciesMojo.groovy:76)

> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi

> nManager.java:483)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa

> ultLifecycleExecutor.java:678)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi

> fecycle(DefaultLifecycleExecutor.java:540)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau

> ltLifecycleExecutor.java:519)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan

> dleFailures(DefaultLifecycleExecutor.java:371)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen

> ts(DefaultLifecycleExecutor.java:332)

> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi

> fecycleExecutor.java:181)

> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)

> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)

> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)

> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

> java:39)

> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

> sorImpl.java:25)

> at java.lang.reflect.Method.invoke(Method.java:597)

> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

> [INFO] ------------------------------------------------------------------------

> [INFO] Total time: 23 minutes 47 seconds

> [INFO] Finished at: Mon Nov 21 09:30:03 MST 2011

> [INFO] Final Memory: 644M/989M

> [INFO] ------------------------------------------------------------------------

I've done some web surfing and others have complained about the same issue. The general consensus is to add -XX:ReservedCodeCacheSize=64m. I've added this to the JAVA_OPTS and to MAVEN_OPTS environment variables but no luck. I've also tried bumping it up to 128m and 256m but still no go.

Any advice would be appreciated.

Environment:

Windows XP SP3

Maven 2.1.0

JDK SE 1.6.0.29

Jira 4.4.1 source downloaded Nov 20

JAVA_OPTS=-XX:ReservedCodeCacheSize=128m

MAVEN_OPTS=-Xmx1024m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=128

3 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Wolfgang Stichling December 3, 2011

I managed to get the build working by repeating the steps documented on the Altassian website on a completely clean identical machine (Windows XP with SP3 + latest updates, 2GB RAM and JDK 1.6.0.29 - nothing else). I found ReservedCodeCacheSize=256m unnessary but I did add MAVEN_OPTS Xms=256m and Xmx=512m as recommended in the maven install instructions. stp/pom.xml was modified as per JRA-25319.

I still have no idea why the other machine won't cooperate.

0 votes
srujan reddy March 6, 2012

Thanks :-).

0 votes
wajdhaikal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 14, 2012

and Try this modification to the batch file set MAVEN-OPT:

-Xmx1024m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=64m

It worked for me.

TAGS
AUG Leaders

Atlassian Community Events