You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Katherine Sanders (JIRA)" <ji...@apache.org> on 2010/03/29 17:54:27 UTC
[jira] Created: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
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
[jira] Assigned: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4666:
--------------------------------------
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
>
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4666.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Added fork=true to maven-compiler-plugin for the integration module. This should fix the issue.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851854#action_12851854 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
r922941 builds without errors on my machine and the next axis2 revision r922967 gets the same out of memory error, so this was caused by the changes in r922967.
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Reopened: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders reopened AXIS2-4666:
--------------------------------------
I'm now getting this error when building the integration module with the latest revision (the same error occurs if I just apply r929538 to the pom.xml in r922967 too):
-------------------------------------------------------------------------------
Test set: org.apache.axis2.om.OMAttributeTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.484 sec <<< FAILURE!
testAttribNamespace(org.apache.axis2.om.OMAttributeTest) Time elapsed: 0.328 sec <<< ERROR!
java.lang.ExceptionInInitializerError
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument$Factory.newInstance(AdviceReqDocument.java:45)
at org.apache.axis2.om.OMAttributeTest.testAttribNamespace(OMAttributeTest.java:43)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder. Make sure the generated binary files are on the classpath.
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument.<clinit>(AdviceReqDocument.java:19)
... 25 more
Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 26 more
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855770#action_12855770 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
The build works fine on Mac OS X as well as on Windows 2003 (with Java 1.6.0_17-b04 and Maven 2.0.11). Also, there is no issue in Hudson [1]. If the issue still persists, then this means that there is something special about your environment or the way you run the build.
[1] http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2/
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855770#action_12855770 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
The build works fine on Mac OS X as well as on Windows 2003 (with Java 1.6.0_17-b04 and Maven 2.0.11). Also, there is no issue in Hudson [1]. If the issue still persists, then this means that there is something special about your environment or the way you run the build.
[1] http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2/
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855770#action_12855770 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
The build works fine on Mac OS X as well as on Windows 2003 (with Java 1.6.0_17-b04 and Maven 2.0.11). Also, there is no issue in Hudson [1]. If the issue still persists, then this means that there is something special about your environment or the way you run the build.
[1] http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2/
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4666.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Added fork=true to maven-compiler-plugin for the integration module. This should fix the issue.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders resolved AXIS2-4666.
--------------------------------------
Resolution: Fixed
I upgraded to maven 2.0.11 and the build is working fine now. Thanks for your help!
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4666:
--------------------------------------
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
>
> 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
[jira] Reopened: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders reopened AXIS2-4666:
--------------------------------------
I'm now getting this error when building the integration module with the latest revision (the same error occurs if I just apply r929538 to the pom.xml in r922967 too):
-------------------------------------------------------------------------------
Test set: org.apache.axis2.om.OMAttributeTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.484 sec <<< FAILURE!
testAttribNamespace(org.apache.axis2.om.OMAttributeTest) Time elapsed: 0.328 sec <<< ERROR!
java.lang.ExceptionInInitializerError
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument$Factory.newInstance(AdviceReqDocument.java:45)
at org.apache.axis2.om.OMAttributeTest.testAttribNamespace(OMAttributeTest.java:43)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder. Make sure the generated binary files are on the classpath.
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument.<clinit>(AdviceReqDocument.java:19)
... 25 more
Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 26 more
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855770#action_12855770 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
The build works fine on Mac OS X as well as on Windows 2003 (with Java 1.6.0_17-b04 and Maven 2.0.11). Also, there is no issue in Hudson [1]. If the issue still persists, then this means that there is something special about your environment or the way you run the build.
[1] http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2/
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Reopened: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders reopened AXIS2-4666:
--------------------------------------
I'm now getting this error when building the integration module with the latest revision (the same error occurs if I just apply r929538 to the pom.xml in r922967 too):
-------------------------------------------------------------------------------
Test set: org.apache.axis2.om.OMAttributeTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.484 sec <<< FAILURE!
testAttribNamespace(org.apache.axis2.om.OMAttributeTest) Time elapsed: 0.328 sec <<< ERROR!
java.lang.ExceptionInInitializerError
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument$Factory.newInstance(AdviceReqDocument.java:45)
at org.apache.axis2.om.OMAttributeTest.testAttribNamespace(OMAttributeTest.java:43)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder. Make sure the generated binary files are on the classpath.
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument.<clinit>(AdviceReqDocument.java:19)
... 25 more
Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 26 more
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4666.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Added fork=true to maven-compiler-plugin for the integration module. This should fix the issue.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852122#action_12852122 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
Are you sure that you did a clean?
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Reopened: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders reopened AXIS2-4666:
--------------------------------------
I'm now getting this error when building the integration module with the latest revision (the same error occurs if I just apply r929538 to the pom.xml in r922967 too):
-------------------------------------------------------------------------------
Test set: org.apache.axis2.om.OMAttributeTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.484 sec <<< FAILURE!
testAttribNamespace(org.apache.axis2.om.OMAttributeTest) Time elapsed: 0.328 sec <<< ERROR!
java.lang.ExceptionInInitializerError
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument$Factory.newInstance(AdviceReqDocument.java:45)
at org.apache.axis2.om.OMAttributeTest.testAttribNamespace(OMAttributeTest.java:43)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder. Make sure the generated binary files are on the classpath.
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument.<clinit>(AdviceReqDocument.java:19)
... 25 more
Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 26 more
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4666.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Added fork=true to maven-compiler-plugin for the integration module. This should fix the issue.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Reopened: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders reopened AXIS2-4666:
--------------------------------------
I'm now getting this error when building the integration module with the latest revision (the same error occurs if I just apply r929538 to the pom.xml in r922967 too):
-------------------------------------------------------------------------------
Test set: org.apache.axis2.om.OMAttributeTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.484 sec <<< FAILURE!
testAttribNamespace(org.apache.axis2.om.OMAttributeTest) Time elapsed: 0.328 sec <<< ERROR!
java.lang.ExceptionInInitializerError
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument$Factory.newInstance(AdviceReqDocument.java:45)
at org.apache.axis2.om.OMAttributeTest.testAttribNamespace(OMAttributeTest.java:43)
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:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder. Make sure the generated binary files are on the classpath.
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:783)
at za.co.eskom.nrs.xmlvend.base.x20.schema.AdviceReqDocument.<clinit>(AdviceReqDocument.java:19)
... 25 more
Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.s16961627B3EA4F7A6561F34500B2DDD4.TypeSystemHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:769)
... 26 more
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852122#action_12852122 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
Are you sure that you did a clean?
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852122#action_12852122 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
Are you sure that you did a clean?
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852122#action_12852122 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
Are you sure that you did a clean?
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851854#action_12851854 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
r922941 builds without errors on my machine and the next axis2 revision r922967 gets the same out of memory error, so this was caused by the changes in r922967.
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851854#action_12851854 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
r922941 builds without errors on my machine and the next axis2 revision r922967 gets the same out of memory error, so this was caused by the changes in r922967.
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders resolved AXIS2-4666.
--------------------------------------
Resolution: Fixed
I upgraded to maven 2.0.11 and the build is working fine now. Thanks for your help!
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders resolved AXIS2-4666.
--------------------------------------
Resolution: Fixed
I upgraded to maven 2.0.11 and the build is working fine now. Thanks for your help!
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Assigned: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4666:
--------------------------------------
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855770#action_12855770 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
The build works fine on Mac OS X as well as on Windows 2003 (with Java 1.6.0_17-b04 and Maven 2.0.11). Also, there is no issue in Hudson [1]. If the issue still persists, then this means that there is something special about your environment or the way you run the build.
[1] http://hudson.zones.apache.org/hudson/view/Axis2/job/Axis2/
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders resolved AXIS2-4666.
--------------------------------------
Resolution: Fixed
I upgraded to maven 2.0.11 and the build is working fine now. Thanks for your help!
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851854#action_12851854 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
r922941 builds without errors on my machine and the next axis2 revision r922967 gets the same out of memory error, so this was caused by the changes in r922967.
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Assigned: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4666:
--------------------------------------
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-4666.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Added fork=true to maven-compiler-plugin for the integration module. This should fix the issue.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851854#action_12851854 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
r922941 builds without errors on my machine and the next axis2 revision r922967 gets the same out of memory error, so this was caused by the changes in r922967.
> 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
[jira] Assigned: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned AXIS2-4666:
--------------------------------------
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852356#action_12852356 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
I wasn't sure what you meant by doing a clean so I did an svn clean, deleted the repository and ran a full axis2 build using "mvn clean install" and the error still occurred.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852356#action_12852356 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
I wasn't sure what you meant by doing a clean so I did an svn clean, deleted the repository and ran a full axis2 build using "mvn clean install" and the error still occurred.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852356#action_12852356 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
I wasn't sure what you meant by doing a clean so I did an svn clean, deleted the repository and ran a full axis2 build using "mvn clean install" and the error still occurred.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852122#action_12852122 ]
Andreas Veithen commented on AXIS2-4666:
----------------------------------------
Are you sure that you did a clean?
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Resolved: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Katherine Sanders resolved AXIS2-4666.
--------------------------------------
Resolution: Fixed
I upgraded to maven 2.0.11 and the build is working fine now. Thanks for your help!
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852356#action_12852356 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
I wasn't sure what you meant by doing a clean so I did an svn clean, deleted the repository and ran a full axis2 build using "mvn clean install" and the error still occurred.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-4666) Out of memory error when compiling
latest revision of axis2 integration module on Windows
Posted by "Katherine Sanders (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852356#action_12852356 ]
Katherine Sanders commented on AXIS2-4666:
------------------------------------------
I wasn't sure what you meant by doing a clean so I did an svn clean, deleted the repository and ran a full axis2 build using "mvn clean install" and the error still occurred.
> 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
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> 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