Sudden increase in JIRA catalina logging levels. Edited

The JIRA catalina.log files started increasing suddenly in size in our JIRA (v6.4.4) to very large, ~6GB/24hrs, from ~250MB/24hrs. There are only three packages set to DEBUG, which are apparently set to DEBUG by default:

com.atlassian.jira.web.filters.ThreadLocalQueryProfiler

com.atlassian.util.profiling

com.atlassian.jira.service.services.DebugService

There seemed to be only INFO messages output up to a certain point, then suddenly many DEBUG messages started being output, for seemingly any action made by a user.

For example:

2017-07-18 03:51:46,192 http-bio-8443-exec-42 DEBUG xxx.xxx 231x1277603x1 1cqq6yg /rest/gadget/1.0/issueTable/filter [velocity.htmlsafe.introspection.AnnotationBoxingUberspect] Got return annotations: []

2017-07-18 03:51:46,192 http-bio-8443-exec-42 DEBUG xxx.xxx 231x1277603x1 1cqq6yg /rest/gadget/1.0/issueTable/filter [velocity.htmlsafe.introspection.AnnotationBoxingUberspect] Getting introspector method for getter: getColumns

2017-07-18 03:51:46,192 http-bio-8443-exec-42 DEBUG xxx.xxx 231x1277603x1 1cqq6yg /rest/gadget/1.0/issueTable/filter [velocity.htmlsafe.introspection.AnnotationBoxingUberspect] got method: public java.util.List com.atlassian.jira.web.component.IssueTableLayoutBean.getColumns()

This was repeated many times for many pages for every action of a user.

It seems like the logging level just suddenly increased, with no apparent user intervention...

 

Any help much appreciated!

2 answers

0 votes
Gaston Valente Community Champion Jul 25, 2017

Alexander,

The filter your executing is working? maybe a change in the custom fields name break it

Thanks Gaston, but the issue seems to be that jira is suddenly logging at a DEBUG level suddenly rather than with a specific operation.

It also does this for other operations such as /secure/AjaxIssueAction!default.jspa 

and /browse/issue-id

So it is not specifc to that filter. Any other ideas?

Gaston Valente Community Champion Jul 25, 2017

Yes, as Matt said, in the administrative section you can set the loggin level of the modules:
Go to 
/secure/admin/ViewLogging.jspa
And check for that

0 votes

Did someone change the top-level log level to DEBUG in System, Logging and profiling? 

 

There seemed to be no change in the logging levels within the Logging and Profiling section.

 

Is there anything that could have triggered a particular logging level to be set to DEBUG automatically?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,080 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you