Closed MohammedFadin closed 4 years ago
We've never seen this before, but looking at the stack trace it's clear that an Archiva thread is unable obtain an fs lock on a file. This is either a problem with how you've deployed Archiva in k8s or with Archiva itself. In either case, this isn't where the issue issue would get resolved - this project is just about the docker image.
I suspect the problem is with how you've deployed Archiva in your cluster, based on a similar issue raised on the Archiva mailing list back in 2014.
I would check to make sure that:
ReadWriteOnce
, since Archiva cannot have different processes modifying it's data volume.Hey @MohammedFadin - I'll leave this open for another day or so, in case you want to follow up with anything.
If you found that the issue was, in fact, due to another process concurrently accessing the file system, then please do indicate that here. In case somebody else bumps into the same problem, I'm sure they would appreciating knowing what happened in your case.
Describe the bug Container randomly throwing errors below.
To Reproduce Randomly
Environment Details Docker Version: Kubernetes 1.14.4_1527 Host OS: OpenJDK8 Image Version: v2.2.4