Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Looking for suggestion related to catalina.out


I know this is not directly related to Jira, but I thought of getting inputs here, since I only have Jira using Tomcat.

The catalina  log file size has grown to 4 GB for me.

I will be implementing a log rotation soon, but that will take time due to various internal approvals.

As a immediate fix, If I delete the existing catalina.out log file, and restart Jira, will it cause any issues? Will a new catalina.out get created or will it complain?

Please suggest.

1 comment

Kurt Klinner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 23, 2019

@Pravin Patil 


Hi Pravin will give you some ideas on the log roation.


One option you could use right away would be 

cat /dev/null > <YOURPATH>/catalina.out


You could also remove the file after you did stop jira, it will be recreated throughout the next start of jira



Like Pravin Patil likes this


Log in or Sign up to comment