[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360558#comment-360558
]
Andreas Gudian commented on SUREFIRE-1132:
------------------------------------------
{quote}
@Andreas
Please recall oracle bug_id sorted by jdk6->jdk8 upgrade - that could be
helpful for me.
{quote}
I can't help you there. At work, we were building with 1.6.0_26 and -T28 (or
something in that order) - everything was fine. Then we switched to 1.6.0_45
and had class-not-found or parser errors in every 10th build or so. After some
weeks we decided to switch to use 1.8.0_25 with targetVersion=1.6 and since
then all was quite again. Switching the JDK to 1.8 there was ok for us, as we
have other, less frequent builds that run with lower parallism and on 1.6.0_45
(without any issues there).
{quote}
Regarding forked booter - i see 3 failures for last 16 hours with the same
error (but in different modules):
{quote}
I take that again these are sporadic issues that sometimes show up and
sometimes don't, right? Do you have the chance to try it out with a recent JDK
8?
> Surefire: regular isolated classloader failures in parallelbuild
> ----------------------------------------------------------------
>
> Key: SUREFIRE-1132
> URL: https://jira.codehaus.org/browse/SUREFIRE-1132
> 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 java.io.IOException: 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
(v6.1.6#6162)
