Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Message-ID: <1531124766.564711269905727528.JavaMail.jira@brutus.apache.org>
Date: Mon, 29 Mar 2010 23:35:27 +0000 (UTC)
From: "Andreas Veithen (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Subject: [jira] Commented: (AXIS2-4666) Out of memory error when compiling
 latest revision of axis2 integration module on Windows
In-Reply-To: <860713281.552941269878067123.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851158#action_12851158 ] 

Andreas Veithen commented on AXIS2-4666:
----------------------------------------

Katherine,

Can you test this after locally reverting the change in r922967? If that solves the issue, then we should try to change the configuration of the maven-compiler-plugin to compile in fork mode.

> Out of memory error when compiling latest revision of axis2 integration module on Windows
> -----------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4666
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4666
>             Project: Axis2
>          Issue Type: Bug
>          Components: Integration
>    Affects Versions: 1.6
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_16
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Katherine Sanders
>
> I get the following error when building the integration module in the latest axis2 revision (r928643):
> [INFO] [compiler:testCompile]
> [INFO] Compiling 519 source files to C:\sandbox\axis2\modules\integration\target\test-classes
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
>         at com.sun.tools.javac.util.Position$LineMapImpl.build(Position.java:139)
>         at com.sun.tools.javac.util.Position.makeLineMap(Position.java:63)
>         at com.sun.tools.javac.parser.Scanner.getLineMap(Scanner.java:1105)
>         at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:512)
>         at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:550)
>         at com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:801)
>         at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727)
>         at com.sun.tools.javac.main.Main.compile(Main.java:353)
>         at com.sun.tools.javac.main.Main.compile(Main.java:279)
>         at com.sun.tools.javac.main.Main.compile(Main.java:270)
>         at com.sun.tools.javac.Main.compile(Main.java:87)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420)
>         at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141)
>         at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493)
>         at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> I originally thought this was a problem with my java version so I tried Sun JDK versions 1.5.0_16, 1.6.0_18 and 1.6.0_16.  I also tried maven 2.08 and 2.09 without any success.  However when I checked out the last revision I was able to build successfully (r912579) it built without errors.  So something must have changed between those revisions that has broken the build on Windows.  I also get the same errors at r927352.
> I spoke to Bill Nagy about this issue last week and he was able to build successfully on Linux with the same maven and jdk version so it's likely this only occurs on Windows.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org