[ 
https://issues.apache.org/jira/browse/MNG-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612061#comment-16612061
 ] 

Michael Osipov edited comment on MNG-6474 at 9/12/18 12:37 PM:
---------------------------------------------------------------

The error does happen if you build in a single thread? Can you please enable 
thread name logging with SLF4J Simple and rerun? 

If you can reproduce this locally, it'd be awesome if you could run also 
Wireshark. She should see the hang if this is socket-related. HAve you tried to 
enable socket timeout in Wagon?


was (Author: michael-o):
The error does happen if you build in a single thread? Can you please enable 
thread name logging with SLF4J Simple and rerun=

> Maven intermittently hanging at end of multithreaded build
> ----------------------------------------------------------
>
>                 Key: MNG-6474
>                 URL: https://issues.apache.org/jira/browse/MNG-6474
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.2
>            Reporter: Beirtí Ó'Nunáin
>            Priority: Major
>         Attachments: Trunk_Build_after_every_commit_UNDEFINED-r15120.log, 
> thread dump.txt
>
>
> I can't reproduce this with a small skeleton project. It has only started 
> happening since we upgraded from 3.3 to 3.5.
>  
> I have a multithreaded multi-module build which builds a number of large 
> (300mb+) artifacts upon SVN commits. I'm running the following goals:
>  
> mvn clean deploy -T 1C
>  
> Reasonably often, perhaps 1 in 10 builds, the build hangs just before where 
> I'd expect the build to have finished. I'm guessing that maven is attempting 
> to install an artifact to the local repository (looking at the stack trace) 
> while the build is about to complete as when I compare the build log from the 
> hung build to a successful build, the following line is the "Reactor Summary"
> This issue happens both on my local machine  and on our TeamCity server (Both 
> multi-processor, multi-core 14 vs 32 cores)
> The Thread dump isn't indicating any kind of DeadLock. Our sysadmins have 
> checked the box for any antivirus scanning which may be impacting the file 
> copy indicated in the log but can't see anything going on at that time.
> Full thread dump from TeamCity attached
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to