java.lang.StackOverflowError #25
Comments
|
If |
|
Thanks, actually I was originally using JDK 1.8 and only later tried 1.7 just to make sure that the problem ist not in the 1.8. Now I installed the latest version of 1.8 and tried it with that, but the result is in my eyes basically the same: |
|
I have the same issue: |
|
Hi, can you provide more details about your environment? Output from With these short stacktraces it might be challenging to reproduce the problem. |
|
Hi, I have the same problem. I attached a test maven project with multiple modules. The "test_integration" module does the integration test for projects "jar_business" and "jar_repositories". During integration test I got: Caused by: java.lang.StackOverflowError |
|
Thanks @bartatamas for sharing the project, I will have a look. |
|
@bartatamas when I disable JaCoCo extension and run the tests against managed WildFly I'm getting this: The issue is that you are fetching too many dependencies to your project (all from the test scope). This line is not needed unless you really use some test specific libraries which are not bundled by arquillian by default (e.g. // Add test dependencies to it
file[] files = Maven.resolver().loadPomFromFile("pom.xml").importTestDependencies().resolve().withTransitivity().asFile();
ear.addAsLibraries(files);But after fixing it I'm facing an issue that either DB is not set (which is not surprising as I cannot find anything for setting it up): Missing config table exception (*click*)So...I cannot reproduce the problem using your project. Any hints from all the others would be more than appreciated. |
|
Hi, Sorry, I forget that this project needs database. Interesting, that when I removed the lines you wrote (import test dependencies) then StackOverflowError disappeared. When I put it back, it appears again. |
|
Those lines are not needed - this might actually be the rootcause as we have for example arquillian dependencies added twice to the project I believe. Another point is - you might consider user include/exclude feature (improved in the last release |
|
i have the same problem with latest version 1.0.0.Alpha9 and jacoco .0.7.8 but i could not delete those lines it send me class not found error |
|
@leccyril could you share your config in the gist? |
|
yes of course ` arquilian.xml: ` and ArquillianDeploymentHelper: `@ArquillianSuiteDeployment }` i run it with testNG but tried with junit same result... code coverage for test unit ok not for Integration tests, jacoco-it.exe is created |
|
i manage to make it work by adding in arquillian.xml include packages, only my local project packages |
|
I have the same problem. If you like me to make a prototype, I may push a new git repo in my account. 16:31:44,351 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."ejb-async-audituser-1.0.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb-async-audituser-1.0.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "ejb-async-audituser-1.0.war" |
|
That would be awesome, so we could try to reproduce. So far I wasn't able to. Can you also give us a bit more context of your environment? |
|
@bartoszmajsak |
|
I have the same kind issue but with nu.validator instead of arquillian. Note that it's a little flickering (I get the StackOverflowError almost all the time but from time to time it's passing). Here is a simple Maven project that reproduce the bug (might help identify in arquillian side): See jacoco/jacoco#528 on jacoco side. |
|
stackOverFlow error is because to much class are scanned with no needed fill the file arquillian.xml with include and exlude class, i manage to make it work with this config and downgrade version of testNG |
|
in my previous post
because in archive deployer to many lib are imported and then scanned... jacoco does'nt support it and moreover does'nt need to scan lib we want to scan our code... |
|
@MatousJobanek |
|
@MatousJobanek |
|
@MatousJobanek JaCoCo is using org.jboss.shrinkwrap.api.exporter.ArchiveExportException: Failed to write asset to output: /WEB-INF/lib/assertj-core-3.6.2.jar |
|
Asm is most likely coming as transitive dependency, can you check how maven is resolving that so we can see why we are having this mess on the classpath? |
|
I checked very big number of source from which ASM is coming. The dependency tree was very big, IDEA run OOM on it. |
|
Does |
|
What about There is no such thing as |
|
i had this problem with apache tika, it had old version of ASM, just make exclusion of aSM in the lib cause issue, in eclipse you can see dependancy hierarchie to see what lib is omitted and replace by what lib... i spet several days on this issue |
|
The ASM problem goes with WildFly and then Arquillian. So I reported an issue in WildFly in order to upgrade ASM and CXF. |
|
For those still limited to an old server (like JBoss EAP 6.4): I have created #72 and I'll try to come up with a PR. |
|
Can someone try the new |
|
I just enabled JaCoCo coverage for our integ tests using this plugin in a Gradle build and am facing a SOE too. For 19 of the tasks the deployment and testing works perfectly fine. and then another 255 times the last 4 lines |
|
Hm, it seems for us here it is because someone managed to many libs to the integTest ear that should not be there, including all kinds of arquillian, shrinkwrap, wildfly JARs. |
Added a jacoco include directive to avoid StackOverFlow. See arquillian/arquillian-extension-jacoco#25
I have the configuration with jacoco-maven-plugin and arquillian-jacoco as described in the README, while using a managed jboss-eap-6.4. Without the jacoco plugin, the tests run fine, but the jacoco plugin causes the StackOverflowError.
... the last two lines repeat for ever.
Please, any idea what is wrong?
The text was updated successfully, but these errors were encountered: