Need help to silence the DEBUG error which is getting logged in jira log file

[nallu]

We are seeing error which gets logged in log file for almost every second. We have no idea from where it is coming and how to fix it. 

Does anyone have any idea?  Please help..

Here is sample error:

2019-07-16 12:02:49,310 http-nio-8080-exec-430 DEBUG kcheung 722x21625054x5 12947o3 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] Crowd query: offset=0, limit=20

2019-07-16 12:02:49,317 http-nio-8080-exec-430 DEBUG kcheung 722x21625054x5 12947o3 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] We did a nice efficient crowd query!

[Matt Doar · Accepted solution]

As Petr said, go to the Logging and Profiling page at /secure/admin/ViewLogging.jspa. Here click on "Configure logging level for another package." 

The name for the package in full is 

com.atlassian.jira.bc.user.search.DefaultUserPickerSearchService

The log messages shorten this name to c.a.j.b but that's not what to use 

Then select a log level such as ERROR to avoid seeing the DEBUG log messages.

[nallu]

Ah thanks @Matt Doar , It worked. As you said, we have to as full package com.atlassian.jira.bc.user.search.DefaultUserPickerSearchService.

thanks a lot!! 

I have wrongly added as 

c.a.j.b.user.search.DefaultUserPickerSearchService

How can I delete this entry from  /secure/admin/ViewLogging.jspa page?? I don't see any delete option there..

[Petr Vaníček · Accepted solution]

Hi,

try go to /crowd/console/secure/admin/loggingProfiling.action in Crowd and add "c.a.j.b.user.search.DefaultUserPickerSearchService" as new class and set it to ERROR level. Then it should be ok. 

[nallu]

Hi @Petr Vaníček , Thanks for taking a look. We are not using Atlassian Crowd at all. We are just using Microsoft Active Directory. 

We never seen these errors in the past. Suddenly, we getting it. 

Recent activity that we did is, 

- Upgraded UPM to latest version 

- Upgraded Script runner to latest version

[nallu]

Do you think, adding new class `c.a.j.b.user.search.DefaultUserPickerSearchService` in the 

/jira/atlassian-jira/WEB-INF/classes/log4j.properties file would fix it???

[Petr Vaníček]

In that case yes, just add it in Jira in same way and let me know.

That isn't error, but debug line.

[nallu]

Hi @Petr Vaníček , 

This is what, I am planning to add

Is this correct?

log4j.logger.c.a.j.b.user.search.DefaultUserPickerSearchService = DEBUG, usersearchlog

log4j.additivity.c.a.j.b.user.search.DefaultUserPickerSearchService = false

[nallu]

Hi @Petr Vaníček 

sorry i dont think this is correct.. I dont know how to add this class 'c.a.j.b.user.search.DefaultUserPickerSearchService' in the log4j property file 

Can you please help me... 

[nallu]

Hi @Petr Vaníček ,

I am going to add a line - 

log4j.logger.c.a.j.b.user.search.DefaultUserPickerSearchService = OFF

[Petr Vaníček]

No, add "c.a.j.b.user.search.DefaultUserPickerSearchService" in /secure/admin/ViewLogging.jspa. Here click on "Configure logging level for another package." and choose ERROR as Level.

[nallu]

No change even after adding above line

[Petr Vaníček]

You mean into file or administration screen as I meantion few min ago?

[nallu]

@Petr Vaníček 

I have tried both cases. None of them doesn't silence the log. 

[Petr Vaníček]

Ok, what do you have in Services (/secure/admin/ViewServices!default.jspa)? What about Scriptrunner (/plugins/servlet/scriptrunner/admin/escalationservices)?

[nallu]

@Petr Vaníček 

We have different services running with below classes...

Services:

com.atlassian.jira.service.services.export.ExportService

com.atlassian.jira.service.services.mail.MailFetcherService

com.atlassian.jira.service.services.mail.MailQueueService

com.atlassian.jira.unbundleordie.valkyrie.registration.ValkyrieRegistrationService

com.atlassian.jira.issue.attachment.store.media.sync.AttachmentSynchronizationService

com.atlassian.jira.avatar.media.AvatarSynchronizationService

Escalation Service:

We have one escalation service to re-index one particular issue type alone. But that too is disabled currently. so i dont think, escalation service is the culprit...

Here is the replication step: 

Whenever, we try to search for a user or try to mention the user the log gets logged. 

2019-07-17 05:03:09,621 http-nio-8080-exec-468 DEBUG shazari 303x22991493x7 w2qt1s 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] Crowd query: offset=0, limit=20

2019-07-17 05:03:09,629 http-nio-8080-exec-468 DEBUG shazari 303x22991493x7 w2qt1s 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] We did a nice efficient crowd query!

2019-07-17 05:03:20,263 http-nio-8080-exec-417 DEBUG pmahendra 303x22991934x6 1bngod5 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] Crowd query: offset=0, limit=20

2019-07-17 05:03:20,271 http-nio-8080-exec-417 DEBUG pmahendra 303x22991934x6 1bngod5 10.6.20.240 /rest/internal/2/user/mention/search [c.a.j.b.user.search.DefaultUserPickerSearchService] We did a nice efficient crowd query!