jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven Integration for Eclipse
  • MNGECLIPSE-505

[mng] StackOverflowError when starting Eclipse

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 0.9.0
  • Fix Version/s: 0.9.9
  • Component/s: Maven Embedder
  • Labels:
    None
  • Environment:
    eclipse.buildId=M20070921-1145
    java.version=1.6.0_05
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fi_FI
    Command-line arguments: -os win32 -ws win32 -arch x86

Description

I've been constantly getting the following exception when starting Eclipse. It's no blocker since it happens only at startup and is most likely caused by faulty poms.

java.lang.StackOverflowError
at sun.nio.cs.UTF_8$Decoder.decodeArrayLoop(UTF_8.java:212)
at sun.nio.cs.UTF_8$Decoder.decodeLoop(UTF_8.java:358)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:544)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:298)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at org.codehaus.plexus.util.xml.XmlReader.read(XmlReader.java:439)
at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2971)
at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3025)
at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1410)
at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1395)
at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4613)
at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4625)
at org.apache.maven.project.build.model.DefaultModelLineageBuilder.readModel(DefaultModelLineageBuilder.java:205)
at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom_aroundBody4(DefaultModelLineageBuilder.java:405)
at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom_aroundBody5$advice(DefaultModelLineageBuilder.java:260)
at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom(DefaultModelLineageBuilder.java:1)
at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resumeBuildingModelLineage(DefaultModelLineageBuilder.java:162)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1027)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:691)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository_aroundBody2(DefaultMavenProjectBuilder.java:213)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository_aroundBody3$advice(DefaultMavenProjectBuilder.java:177)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:1)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository_aroundBody0(DefaultMavenProjectBuilder.java:202)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository_aroundBody1$advice(DefaultMavenProjectBuilder.java:177)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:1)
at org.apache.maven.project.DefaultMavenProjectBuilder.mergeManagedDependencies(DefaultMavenProjectBuilder.java:1118)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:748)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository_aroundBody2(DefaultMavenProjectBuilder.java:213)

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MNG-3391 StackOverflowError in DefaultMavenProjectBuilder

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Eugene Kuleshov added a comment - 28/Mar/08 12:55 PM

Tuomas, please verify is you still have the same problem with the latest 0.9 build available from the new update site at http://m2eclipse.sonatype.org/update/

If it still there, we would really need a test project that would allow us to reproduce this issue.

Show
Eugene Kuleshov added a comment - 28/Mar/08 12:55 PM Tuomas, please verify is you still have the same problem with the latest 0.9 build available from the new update site at http://m2eclipse.sonatype.org/update/ If it still there, we would really need a test project that would allow us to reproduce this issue.
Hide
Permalink
Tuomas Kiviaho added a comment - 31/Mar/08 3:10 AM

I'm actually using 0.9 (from sonatype) already. I have ~20 open projects currently on my workbench and some of them are deeply nested multimodule projects so it might take a while for me to pull out reproducible project.

Show
Tuomas Kiviaho added a comment - 31/Mar/08 3:10 AM I'm actually using 0.9 (from sonatype) already. I have ~20 open projects currently on my workbench and some of them are deeply nested multimodule projects so it might take a while for me to pull out reproducible project.
Hide
Permalink
Marcello Teodori added a comment - 31/Mar/08 8:49 AM

I get the same error in a project using ServiceMix with deeply nested modules when importing as Maven Project.

I've found a reference to this kind of issue also on the Maven JIRA when trying to compile the smx3 trunk, and I've verified the same error happening checking out from SVN and importing the project as Maven Project like mine:
http://jira.codehaus.org/browse/MNG-3391

Something similar has also been experienced by the q4e guys:
http://code.google.com/p/q4e/issues/detail?id=220

It seems to be a recursion problem originating from the Maven Embedder.
Unfortunately the error happens even changing in the preferences the Maven Runtime to an external 2.0.8 installation.

For the sake of completeness, I've also tried to import the Archiva SVN, which was quite nested as well, and everything worked there, I don't know if there is some connection between this error and the maven plugin used by servicemix to build the JBI artifacts using custom packaging types which leverages the dependency mechanism in a similar way to the ear packaging plugin.

Show
Marcello Teodori added a comment - 31/Mar/08 8:49 AM I get the same error in a project using ServiceMix with deeply nested modules when importing as Maven Project. I've found a reference to this kind of issue also on the Maven JIRA when trying to compile the smx3 trunk, and I've verified the same error happening checking out from SVN and importing the project as Maven Project like mine: http://jira.codehaus.org/browse/MNG-3391 Something similar has also been experienced by the q4e guys: http://code.google.com/p/q4e/issues/detail?id=220 It seems to be a recursion problem originating from the Maven Embedder. Unfortunately the error happens even changing in the preferences the Maven Runtime to an external 2.0.8 installation. For the sake of completeness, I've also tried to import the Archiva SVN, which was quite nested as well, and everything worked there, I don't know if there is some connection between this error and the maven plugin used by servicemix to build the JBI artifacts using custom packaging types which leverages the dependency mechanism in a similar way to the ear packaging plugin.
Hide
Permalink
Eugene Kuleshov added a comment - 31/Mar/08 7:12 PM

Guys, I just pushed new build. New embedder should include fix for this issue, but I haven't got chance to test it with ServiceMix project yet.

Show
Eugene Kuleshov added a comment - 31/Mar/08 7:12 PM Guys, I just pushed new build. New embedder should include fix for this issue, but I haven't got chance to test it with ServiceMix project yet.
Hide
Permalink
Tuomas Kiviaho added a comment - 01/Apr/08 6:46 AM

I've got ServiceMix (3.2.1) dependencies as well on my workbench. I tried the plugin using PDE Tools>Build Site but the error remained. Although the Manage Configuration dialog points to the org.maven.ide.eclipse_0.9.1.200804011322 version (I guess) the old version of embedder is still somehow used even though -clean option was used. Is there a snapshot update site that I'm unaware of where prebuild versions could easily be fetched.

I noticed that there are POMs available, but I don't think they've been tested yet with CI since I found a works-on-my-machine anti-pattern from one of them when I tried to compile them.

Index: m2eclipse/org.maven.ide.components.pom/pom.xml
===================================================================
— m2eclipse/org.maven.ide.components.pom/pom.xml (revision 116)
+++ m2eclipse/org.maven.ide.components.pom/pom.xml (working copy)
@@ -20,7 +20,7 @@

<groupId>org.maven.ide.components</groupId>
<artifactId>org.maven.ide.components.pom</artifactId>

  • <version>${maven_model_edit.version}</version>
    + <version>${maven_pom.version}</version>

<name>Maven Project Model</name>

Show
Tuomas Kiviaho added a comment - 01/Apr/08 6:46 AM I've got ServiceMix (3.2.1) dependencies as well on my workbench. I tried the plugin using PDE Tools>Build Site but the error remained. Although the Manage Configuration dialog points to the org.maven.ide.eclipse_0.9.1.200804011322 version (I guess) the old version of embedder is still somehow used even though -clean option was used. Is there a snapshot update site that I'm unaware of where prebuild versions could easily be fetched. I noticed that there are POMs available, but I don't think they've been tested yet with CI since I found a works-on-my-machine anti-pattern from one of them when I tried to compile them. Index: m2eclipse/org.maven.ide.components.pom/pom.xml =================================================================== — m2eclipse/org.maven.ide.components.pom/pom.xml (revision 116) +++ m2eclipse/org.maven.ide.components.pom/pom.xml (working copy) @@ -20,7 +20,7 @@ <groupId>org.maven.ide.components</groupId> <artifactId>org.maven.ide.components.pom</artifactId>
  • <version>${maven_model_edit.version}</version> + <version>${maven_pom.version}</version>
<name>Maven Project Model</name>
Hide
Permalink
Eugene Kuleshov added a comment - 01/Apr/08 8:41 AM

Tuomas, sorry, I am not quite following your last comment. Does or does not ServiceMix project work with last m2eclipse release? Please don't mix several issues in this bug report.

Show
Eugene Kuleshov added a comment - 01/Apr/08 8:41 AM Tuomas, sorry, I am not quite following your last comment. Does or does not ServiceMix project work with last m2eclipse release? Please don't mix several issues in this bug report.
Hide
Permalink
Tuomas Kiviaho added a comment - 01/Apr/08 9:33 AM

Neither 0.9.0.20080310-1400-Sonatype nor 0.9.1.200803311600 work (latter I built today from the sonatype trunk with PDE Tools>Build Site). When servicemix references are removed the project my original workbench will not end up this error anymore.

A new project on a fresh workbench containing just the following dependency will recreate the problem.
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-jbi</artifactId>
<version>3.2.1</version>
</dependency>

What bothered me was that the stacktrace lines were identical with both versions of the plugin leading me to suspect whether or not I had managed to build the plugin correctly.

Show
Tuomas Kiviaho added a comment - 01/Apr/08 9:33 AM Neither 0.9.0.20080310-1400-Sonatype nor 0.9.1.200803311600 work (latter I built today from the sonatype trunk with PDE Tools>Build Site). When servicemix references are removed the project my original workbench will not end up this error anymore. A new project on a fresh workbench containing just the following dependency will recreate the problem. <dependency> <groupId>org.apache.servicemix</groupId> <artifactId>servicemix-jbi</artifactId> <version>3.2.1</version> </dependency> What bothered me was that the stacktrace lines were identical with both versions of the plugin leading me to suspect whether or not I had managed to build the plugin correctly.

People

  • Assignee:
    Unassigned
    Reporter:
    Tuomas Kiviaho
Vote (0)
Watch (0)

Dates

  • Created:
    28/Mar/08 5:59 AM
    Updated:
    23/Oct/08 4:55 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.