I saw a tweet by Simon Haslam at the weekend that read,
“I’m v surprised to read that @Atlassian Stash needs newer git than in the latest RHEL/OL6 repos!”
“Apache Tomcat Release 7.0.56 or later”
So let’s have a look at what is typically available from the Yum repositories at the time of writing.
- RHEL6/OL6 : tomcat6-6.0.24-80.el6.x86_64.rpm
- EPEL 6 : tomcat-7.0.33-4.el6.noarch.rpm
- RHEL7/OL7 : tomcat-7.0.42-8.el7_0.noarch.rpm
Realistically, nobody is moving to RHEL7/OL7 for Oracle products yet, since the only database version certified is Oracle 12c (22.214.171.124 onward), so the vast majority of kit out there will be running RHEL6/OL6. With that in mind, the requirement for “Apache Tomcat Release 7.0.56 or later” represents a bit of a support nightmare. As soon as people require a piece of software on a server that is not available from a default (or similar) Yum repository, the product is outside the typical sys admin patching cycle and someone has to make a specific effort to keep the custom installation up to date. You know what that means right? Yeah, it never gets patched… It’s not that installing this stuff is difficult. It’s just the impact it has on sys admin teams that is the problem.
We all want to use the latest and greatest, but there seems to be a disconnect between what the developers do and what is reasonably supportable out here in the real world. Developing stuff against product versions that are not in Yum repos is a mistake IMHO.
I’m going to play around with ORDS on older versions of Tomcat to see what happens…