Nexus Repository 3 Logger Reference


Repository manager default logger levels are intended to be verbose enough to help diagnose problems should they be encountered and quiet enough to not create overly large log files.

Increasing default log output verbosity can be used when more information needs to be gathered about a problem or activity. In some cases making a logger less verbose is justified to avoid spamming the application log with noisy messages.

This article serves as a reference to some of the loggers commonly adjusted by feature area. This is not a complete list and not all loggers are available in all versions of repository manager.

Logging Postgresql/H2 SQL Database Queries

Database Access Objects perform the actual SQL queries against the database. These logger names always end with "DAO". Depending on the feature area you want to debug, enabling DEBUG level for these loggers can help expose the actual database queries being made. Enabling DEBUG for these in production is highly cautioned. In some cases sensitive information may be exposed or the output may be very verbose. Test first.

Nexus Repo code can be grepped for a listing of all these DAO classes. For example this command against ~3.44.0 source code shows 161 individual loggers:

find . -name '*' | rg --invert-match 'src/test|example' | rg '.*/((com|org).*)\.java' -r '$1' | sed 's/\//./g' | wc -l

The sample list is output below:

> find . -name '*' | rg --invert-match 'src/test|example' | rg '.*/((com|org).*)\.java' -r '$1' | sed 's/\//./g'


Diagnose LDAP Queries and LDAP Server Connection Stack Traces

  • set logger to DEBUG

Repository Formats


  • set to DEBUG


Diagnose Outbound Webhook Payloads

  • set to DEBUG

Example log entries:

2016-12-14 17:09:43,902+0000 DEBUG [event-1-thread-2] admin - Sending webhook request: WebhookRequest{id='9d80527e-8f7d-455a-a86b-191e9ac7ab9e', webhook=rm:repository:component,$RepositoryComponentWebhookPayload@2a89735b, url=}
2016-12-14 17:09:44,420+0000 DEBUG [event-1-thread-2] admin - Sending POST request: POST HTTP/1.1
2016-12-14 17:09:44,736+0000 DEBUG [event-1-thread-3] admin - Sending webhook request: WebhookRequest{id='29608664-b00b-4e1a-af3d-d0ced495fd57', webhook=rm:repository:component,$RepositoryComponentWebhookPayload@9ef9b8, url=}
2016-12-14 17:09:44,760+0000 DEBUG [event-1-thread-3] admin - Sending POST request: POST HTTP/1.1
2016-12-14 17:09:44,765+0000 DEBUG [event-1-thread-2] admin - Response status: HTTP/1.1 200 OK
2016-12-14 17:09:44,996+0000 DEBUG [event-1-thread-3] admin - Response status: HTTP/1.1 200 OK

If there is an error in posting to the webhook url, then you will see an error like the following:

2016-12-14 16:40:34,567+0000 ERROR [event-1-thread-16] admin - Failed to send webhook request: WebhookRequest{id='071b719e-683d-4fb4-a031-12e292ed4ec0', webhook=rm:repository:component,$RepositoryComponentWebhookPayload@76beefa6, url=}
org.apache.http.client.HttpResponseException: Not found


Diagnose UI Search Inbound JSON Payloads

  • set to DEBUG


Log SAML Related Activity

  • set  to DEBUG
  • set org.keycloak.saml to DEBUG


Have more questions? Submit a request


Article is closed for comments.