To keep track of the Archiva performance and problems, log files are created during runtime. These files can be found in the logs/ directory.
- archiva.log - contains all the start-up information and output logs for Archiva
- archiva-audit.log - contains information regarding the operations performed against the repositories and configurations being modified. A good example is when an artifact is deployed to an Archiva repository. The operation will be logged in this file, with the date and timestamp of when the operation occurred, the userId of who performed the deployment, and the artifact that was deployed.
- archiva-security-audit.log - contains information regarding Archiva's security. For example, a successful login of a user or a user account is created.
Note since 1.4-M4, the log4j2 asyncLogger feature is configured per default.
This mean per default AsyncLogger.WaitStrategy option is configured to Sleep.
If you are on a constrained environment, you can change it to Block (-DAsyncLogger.WaitStrategy=Block) (See log4j2 documentation )