Hi Olivier, Am 17.04.2014 01:24, schrieb Olivier Lamy: > DefaultISMLocking is a jackrabbit class > > Maybe try change the log4j2 async configuration? > See http://archiva.apache.org/docs/2.0.2-SNAPSHOT/adminguide/logging.html > Due to various issues reported here, I will change the default.
We've already changed that, didn't change anything (we have no CPU issue here). Also in the meantime I added 4 more cores (so currently 8) - average load is at 2, so plenty of free CPU cycles for Archiva. Do you have any idea about the other things? Or a starting point where we should debug / profile?
