After some time catalina.out can grow significantly and system can run out of space. This can happen for several reasons. Here we try explain some of them 🙂


SSL Error

As explained in this page, a SSL Warning from MySQL fill own Catalina.out file (both Confluence and Jira can have this issue). This is a sample of log row:

2017-07-13 16:16:14,155 http-nio-8080-exec-2 ERROR user_name 976x20x1 n9r5jf, /secure/Dashboard.jspa [c.a.g.r.internal.http.HttpClientFetcher] Unable to perform a request to: PKIX path building failed: unable to find valid certification path to requested target

A solution is insert a specific parameter in MySQL Connection string: useSSL=false like this:


and Catalina.out will not filled with that warning message 🙂


Reduce logging on Catalina.out

Everything is logged in Catalina.out by Tomcat and this can be a problem if own instance have a lot of usage. Working with a copy of, we can delete all console entry like this example:

[Original] = WARN, console, filelog
[Modified] = WARN,  filelog

This reduce the amount of log written in Catalina.out. My personal suggestion is: keep a copy of file with all console entry and use it when you need a verbose log file. After put the copy without console entry for everyday work.


Log Rotate Catalina.out

If the previous suggestion is not definitive, introduce a log rotate for Catalina.out. Following all the steps in this Jira tutorial, so we can reduce the size of Catalina.out 🙂

By Fabio, Artigiano del Software in MrAddon

Posted by:artigianodelsoftware

One thought on “Catalina.out Big Size – How to manage

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s