You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
At this moment we are running with Tomcat 8.5.79 with no problem
Given 8.13 is a long term support version of Jira, you should be able to update to 8.13.27 (latest release) and get all the big/security fixes without impacting functionality.
do you have any concerns about moving to 8.13.27?
CCM
Hi @Roser Carbonell, welcome! I wouldn't recommend updating to a newer version of Tomcat without updating the Jira version.
Here's another post that I agree with:
Solved: Upgrading Tomcat ONLY (atlassian.com)
Yes, it probably would work, but if Atlassian didn't test their code with it, and you run into issues, you could cause bigger problems. I would see if you can update to a newer Jira Server version that would include that Tomcat version (or newer) to solve the issue you are having.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.