Howdy Dan, You did not mention what locking implementation you use, what params etc? file-lock? redisson? something else?
At the same time, it is rather strange that you mention "at the same artifact" thing... from here and below I will assume you use file locks: - can you do something like lsof on Linux? Meaning, can you ensure nothing (some app, IDE or antivirus) is keeping the file open? - can you tell a bit more about that artifact? Is it installed one? Maybe from the current build? A dependency? In case of HUGE build and COMMON artifact (ie. slf4j-api) that is used in almost all modules may be "hot", maybe try to increase lock timeout? Or even radically lessen (that should make problem occur more often perhaps) HTH Tamas On Wed, Mar 22, 2023 at 7:32 PM Dan Tran <dant...@gmail.com> wrote: > Hi > > My large 400+ modules build facing the mentioned locking issue consistently > at the same artifact > > artifact:ch.qos.logback:logback-classic:1.2.10 > > > any one see this issue at your build? > > > Thanks > > > -D > > > dont see same issue at smaller build >
