Error creating bean with name 'authenticationInterceptor#rest' about docker-archiva

[tkent]

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:

1. Archiva data PV is configured as ReadWriteOnce, since Archiva cannot have different processes modifying it's data volume.
2. You don't have any sidecar containers that might be locking the files on the Archiva data volume in the pod you're using (this is possible if you're not using our xetusoss-archiva helm chart to deploy Archiva)

[tkent]

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.