JBoss EAP 7 in ELS‑1?

Here’s Your Developer‑Friendly Upgrade Path

Keep javax.*, stay on Java EE 8, and modernize on your terms — with Payara Platform Enterprise 5.

Why This Matters Now (for developers)

When Red Hat moved JBoss EAP 7 into Extended Life Cycle Support (ELS‑1), it changed your day‑to‑day: fewer updates, diminishing certifications, and increasing friction upgrading JVMs, databases, and infra.

What you’re seeing:

  • Security and bug fixes only, and delayed → longer exposure windows
  • No new features / enhancements → stagnating performance & tooling
  • Compatibility risk → not certified against newer JVMs or DBs
  • Rising cost for less → ELS surcharges with shrinking value

What you want instead:

  • A stable, supported Java EE 8 runtime with javax.* continuity
  • Monthly updates (bugs & security) and maintained container images
  • Predictable SLAs & expert help to unblock releases
  • Time and flexibility to modernize incrementally (when you decide)

Your Options

With JBoss EAP 7.x reaching ELS-1, you can choose between limited legacy support, security,
ROI or full control over your Java future by migrating to Payara Platform Enterprise 5.

Remain on JBoss EAP 7 (ELS‑1)Move to JBoss EAP 8Migrate to Payara Enterprise 5
GeneralAt tick Minimal change nowAt tick Stay in the Red Hat/JBoss ecosystemAt tick Migration to a highly compatible alternative
Support EndsCross Mark ELS-1 in 2027 → ELS-2 no updatesCross Mark Full support for JBoss EAP 8 ends in 2028At tick Guaranteed to 2031
Cost ModelCross Mark Paid ELS extensionsCross Mark License is typically more expensiveAt tick Full support included
Security UpdatesCross Mark Limited / delayedCross Mark Limited / delayedAt tick Regular patches + hot fixes
ModernizationAt tick No refactoring requiredCross Mark Migration require namespace changeAt tick No refactoring required
ComplianceCross Mark UnreliableCross Mark Certifications maintained until 2028At tick Actively maintained certifications
Vendor Lock-inCross Mark HighCross Mark High riskAt tick Highly portable
SupportCross Mark BasicCross Mark Infrequent releasesAt tick Enterprise SLA coverage

What Dev Teams Get with Payara 5

  • Drop‑in Java EE 8 runtime: preserve your codebase and keep your release cadence
  • Monthly releases: security patches, bug fixes, and platform improvements
  • DevOps‑ready: maintained container images; automation‑friendly administration
  • Expert support: real engineers on the line, with SLAs that match enterprise needs
  • Compliance‑aligned: proactive fixes and lifecycle you can plan around

“In terms of support costs Payara is 60% cheaper than JBoss… Our engineers are extremely satisfied with Payara’s performance.” — Best Western, Hotels & Resorts

Migration: Fast Path for Developers

Most teams complete an initial lift‑and‑shift in days, not months.
  • Inventory your datasources, JMS, security realms, and scheduled jobs
  • Stand up Payara Enterprise 5 in a non‑prod environment (VM or container)
  • Map configuration one‑to‑one (JDBC pools, JMS, realms) with parity configs
  • Deploy existing EAR/WARs unchanged (Java EE 8, javax.*) and smoke test
  • Iterate: performance tuning, HA cluster setup, and CI/CD pipeline updates

Architecture & Operations Highlights

  • Clustering & Session Replication for scale and resilience
  • Managed Data Sources & Connection Pools with observability defaults
  • Transaction Management & Messaging aligned with Java EE 8
  • Lifecycle & Patch Cadence designed for enterprise change windows

For Tech Leads

Plan it like a change, not a rewrite.
  • Scope: runtime swap + config parity
  • Risk controls: canary deployments, rollback plan, perf baseline
  • Success criteria: zero code changes, security posture improved, patch cadence restored
Migrating from JBoss EAP to Payara Server Enterprise

What to Do Next

Ready to move forward? Whether you want to test compatibility quickly or validate Payara in your own environment, choose the path that best fits your workflow. Both options are designed to get you hands-on with minimal risk and maximum clarity.

Path A — Evaluate quickly (no heavy lift):
  • Get the Migration Playbook (config map, test plan, rollback strategy)
  • Book a 30‑minute technical consultation with a Payara engineer
Path B — Pilot in your stack:
  • Spin up a non‑prod Payara 5 environment
  • Deploy a representative app; capture perf & compatibility; iterate

Trusted by Global Leaders Across Industries

With a relentless focus on stability, security, and flexibility, Payara enables
enterprises in unlocking the full value of their Java investments.

Talk to a Payara Engineer
About Your JBoss Upgrade

Get expert guidance on upgrading from JBoss EAP 7 — architecture review, migration options, and a clear next step tailored to your application.