redhat jboss eap end of life dates — full support timeline
5 of 6 tracked redhat jboss eap releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 8 | 2024-02-05 | 2031-02-05 | 8.1.5 | supported |
| 7 | 2016-05-01 | 2025-06-30 | 7.4.23 | ended |
| 6 | 2012-06-01 | 2019-06-30 | 6.4.24 | ended |
| 5 | 2009-11-01 | 2016-11-30 | 5.2.0 | ended |
| 4.3 | 2008-01-01 | 2013-01-31 | 4.3.0 CP10 | ended |
| 4.2 | 2007-06-01 | 2012-06-30 | 4.2.0.CP09 | ended |
Who is affected
Anyone running an unsupported redhat jboss eap release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/redhat-jboss-eap, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next redhat jboss eap deadline
You are reading this because a redhat jboss eap release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every redhat jboss eap and related deadline as it is announced, with exact dates and primary sources.
Watch redhat jboss eap deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.