maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <>
Subject [jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
Date Thu, 01 Jan 2015 17:15:10 GMT


Andreas Gudian commented on SUREFIRE-1132:

@Tibor: as the build is fine with single threads, the involved jars should be ok already,
and I guess a single project wouldn't help us investigating the issue.

@Alexander: as I wrote, please try using {{forkCount=1}} if that is possible, as it gives
you much more isolated classloader behaviour.

Please let us know if that works, and then we can check what might be wrong with the classloaders
in the parallel builds. It could also be some other plugin that manipulates the test-dependencies
in an illegal, not thread-safe way...

Other than that I can say that I have also seen resources vanishing from a classloader in
a longer running application (at start they are there, and then, at some later point they
suddenly can't be loaded anymore). But that was an older Java 6 version some years ago. But
7u25 is rather old as well, so that can't be dismissed completely as a possible point of failure.

> Surefire: regular isolated classloader failures in parallelbuild
> ----------------------------------------------------------------
>                 Key: SUREFIRE-1132
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 2.17
>         Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux
> windows server 2008 x64
> Maven 3.2.2, 3.2.3, 3.2.5
> Oracle HotSpot JDK 7u25
>            Reporter: Alexander Ashitkin
>         Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt
> We have a large project of 300+ modules which regularly fails with different kind of
classloading issues in different places in surefire plugin. The issue is reproduced only with
parallel build and is not reproduced in single threaded. This is a main contributor in build
instability for us. All the not loaded dependnecies are actually present in dependency tree.
I attached 3 different samples of how build fails.
> Surefire config:
> {code}
>                     <configuration>
>                         <forkCount>0</forkCount>
>                         <!--doesnt work in parrallel build. Causes build failures
with error Stream Closed-->                      <redirectTestOutputToFile>false</redirectTestOutputToFile>
>                         <useManifestOnlyJar>false</useManifestOnlyJar>
>                     </configuration>
> {code}
> maven cmd is like install -T 10
>  Please advise how to sort this out - ready to run any provided diagnostic and evaluate
any options.
> Thanks in advance, Alexander

This message was sent by Atlassian JIRA

View raw message