Oracle WebLogic Support & Platform Migration

Oracle WebLogic Support and Platform Migration

Last reviewed by Tyler Eastridge

AceMQ gives enterprise teams 24/7 engineering support for Oracle WebLogic Server 12.2.1.4, 14.1.2 and 15.1.1, and plans the move to Tomcat, WildFly or JBoss EAP, Payara or Open Liberty when you decide to leave. AceMQ engineers lead each engagement and partner WebLogic specialists do the WebLogic-specific work, under one AceMQ contract. AceMQ is independent of Oracle: it produces no Oracle patches, gives no licensing advice and does not rewrite application code.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without a rewrite or a forced renewal decisionFor production incident cover, see AceMQ WebLogic 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about WebLogic

Eight WebLogic problems AceMQ is set up to work on, from a release whose Oracle Premier Support ends in December 2026 to a stuck-thread storm nobody can trace and a migration that was scoped as just WAR files.

  1. 01

    Premier Support for WebLogic 12.2.1.4 ends in December 2026 and nobody has decided between Extended Support, an upgrade and a move

  2. 02

    Managed servers go into a stuck-thread state under load and the thread dumps are read by nobody who has seen them before

  3. 03

    A JDBC pool is exhausted every month-end and the fix keeps being a bigger pool

  4. 04

    JMS messages pile up in a file store after a consumer fails, and nobody knows which destinations the code depends on

  5. 05

    Two domains that should be identical differ in config.xml because people edit them by hand

  6. 06

    The one person who writes the WLST scripts is leaving, and the scripts are the only documentation

  7. 07

    The security scanner flags T3 and JNDI exposure and the patch level is quarters behind

  8. 08

    A move to Tomcat was scoped as just WAR files, and then the EJBs and JMS destinations turned up

A good fit if you run WebLogic in production and need engineers who can be on a bridge with response targets from 15 minutes, by plan, or want a written map of what a move to another server would involve before you commit to one.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy WebLogic.

Running WebLogic in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What happens when a WebLogic application moves to another server and its JNDI names and data sources do not come across?

A WAR or EAR file is the small part of a WebLogic application. The server around it supplies JNDI-bound data sources, JMS destinations, security realms and deployment descriptors, and none of them travels with the archive. A first deployment to a new server often fails on some nodes and passes on others.

First deployment to the new server, two nodes failing

One application, the target server and three cluster nodes

Illustrative
  1. Three managed servers run the application. Its data source, JMS destination and JNDI names are defined in the domain, and nobody has written them down outside config.xml.

  2. The archive is deployed to the new server. Nodes 1 and 2 fail at startup: a JNDI name bound by the WebLogic data source is missing and a JMS destination has no provider. Node 3 starts because someone created its data source by hand during a test, so the failure looks intermittent.

  3. A read-only inventory of the domain lists every JNDI name, data source, JMS destination and descriptor setting. The target is configured from that list, the cluster is rehearsed against a copy of production data, and the old domain stays as the rollback until cutover.

The failure is rarely in the archive. It is in what the server supplied around it: data sources with their pool settings, JNDI names the code looks up, JMS destinations and stores, work managers, security realms, session replication on the cluster and T3 clients that call EJBs. The namespace matters as well. WebLogic 14.1.2 runs the javax namespace and 15.1.1 runs jakarta, so a target is chosen on the namespace your code already uses. A javax application that moves to a jakarta-only server needs code changes, which AceMQ plans around and does not make. Tomcat 9.0 still runs javax, and its support is expected no earlier than 31 March 2027, so that route is short. An inventory, a mapping and a rehearsal are the first AceMQ deliverables.

Our Services

WebLogic Consulting & Services

AceMQ runs five WebLogic service lines: platform migration assessment, production support, lifecycle and patch planning, a fixed-scope health check, and hardening and access review. Any of them can roll into 24/7 on-call with response targets from 15 minutes, by plan. Rewriting application code is not one of them.

  • 01

    Platform Migration Assessment

    A written map of what moving a WebLogic estate to Tomcat, WildFly or JBoss EAP, Payara or Open Liberty would involve, before anyone commits to a target.

    • Inventory of domains, clusters, data sources, JNDI names and JMS destinations
    • Mapping of descriptors and WebLogic APIs to each target
    • Namespace check: javax or jakarta, against each target's support window
    • Rehearsal and cutover plan with the old domain as the rollback
  • 02

    Production Support

    Engineers on a bridge when a domain is down or slow: thread dumps, pool exhaustion, JMS backlogs, cluster membership and memory.

    • On-call escalation with response targets from 15 minutes, by plan; 24/7
    • Stuck-thread, connection pool and JMS backlog diagnosis
    • Written root-cause analysis after every P1
    • Works with your admins or covers a gap in the team
  • 03

    Lifecycle and Patch Planning

    A plan against Oracle's published dates for the releases you run, and the quarterly patch windows that come with them.

    • Premier and Extended Support dates by release
    • Quarterly patch window planning and rollback
    • Upgrade path from 12.2.1.4 to 14.1.2 or 15.1.1
    • Patches themselves come from Oracle under your contract
  • 04

    WebLogic Health Check

    The fixed-scope entry engagement: a written report on the state of the domains that your own team can act on, with or without AceMQ afterwards.

    • Domain configuration and drift between environments
    • Thread, work manager and connection pool settings
    • JMS server and store review
    • Ranked remediation list with owners
  • 05

    Hardening and Access Review

    The configuration findings a scanner or auditor raises on the domains you point us at.

    • T3 and IIOP exposure and network filtering
    • Admin console and Node Manager access
    • The gated JNDI and T3 security features in 15.1.1 Critical Security Patch Updates
    • Operating-system and JVM settings behind the server
  • Response targets from 15 minutes, by plan

    24/7 WebLogic Support

    Senior engineers briefed on your environment, response targets from 15 minutes, by plan, and no ticket routing.

    • Response targets from 15 minutes, by plan
    • Senior engineers, no first-line triage layer
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your WebLogic estate.

Contact Us

24/7 Support

WebLogic Support When It Matters Most

AceMQ WebLogic support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when a domain is down or production is failing, 24/7. Lower severities get 1-hour, 4-hour and next-day responses. Patches still come from Oracle: AceMQ does not produce them.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Engineers Who Know Your Environment

    Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.

  • Proactive Risk Mitigation

    Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

How It Works

What actually happens next

An AceMQ WebLogic engagement runs in four stages: a scoping call with a quote within 1 hour, a read-only inventory of your domains, a written plan that maps each dependency to a target or a fix, then rehearsed changes and on-call. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: releases, how many domains and clusters, which applications, JMS and JDBC use, who is on call today and what is driving the question. A quote request is answered within 1 hour.

Scoped per estate

Read-only inventory

A read-only review of each domain: servers and clusters, data sources, JNDI names, JMS destinations and stores, security realms, deployment descriptors and patch level. Nothing in production changes, and the findings are written and ranked by risk.

Scoped per estate

Plan and mapping

A written plan that maps each dependency to a fix on WebLogic or an equivalent on a target server, with the code changes a target would force listed separately for your team or another provider. Support cover starts here if you want it.

Ongoing

Rehearse, change, run

Rehearsals on a copy of the environment, staged changes with the old domain kept as the rollback, and on-call response with response targets from 15 minutes, by plan. A written review follows every patch window or incident.

  • Written findings before any change
  • Changes staged and reversible, with the old domain kept as the rollback
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Platform migration

Moving off WebLogic: the order a platform migration runs in

A WebLogic platform migration changes the server your applications run on and leaves the applications themselves alone. AceMQ plans it, rehearses it and supports the cutover. Changes to application code are listed for your team to make and are outside AceMQ's scope. This is the order the work runs in.

Inventory

Read what the domain supplies

List every data source, JNDI name, JMS destination, security realm, work manager and deployment descriptor in each domain, from config.xml and the application archives, without changing anything.

Choose

Match the target to the namespace

WebLogic 14.1.2 runs the javax namespace and 15.1.1 runs jakarta. Tomcat 9.0 runs javax and its support is expected no earlier than 31 March 2027, while Tomcat 10.1 and 11.0 run jakarta. The target follows from the code you have and the code you will change.

Rehearse

Build the target from the inventory

Configure the target server from the list, run the application against a copy of production data, and compare behaviour under load: thread use, pool use and message flow. Messaging moves to an external broker where the target has none.

Cut over

Switch traffic with a way back

Move traffic in stages. The WebLogic domain stays intact as the rollback until the new server has run a full business cycle, then it is retired on your schedule.

Typical engagements

How WebLogic engagements run

Typical engagements from AceMQ on WebLogic and the servers it moves to, with the environment, what AceMQ assesses and what the engagement delivers. Each card links to the full write-up.

  • From our platform practice

    Java Estate Inventory and OpenJDK Distribution Selection

    Mid-Sized Distribution Company

    A typical engagement for a company that wants to leave an Oracle Java SE subscription or avoid one: inventory every Java runtime, compare OpenJDK distributions against the estate, and write the migration plan.

    JavaOpenJDKDockerKubernetes
  • From our platform practice

    Java Services Killed by the Container Memory Limit After a JDK Upgrade

    SaaS Platform Team

    A typical engagement for Java services that restart with exit code 137 after a base image brings a newer JDK: the heap is not full, no OutOfMemoryError appears, and the memory that matters lives outside the heap.

    JavaKubernetesDockerPrometheus
All use cases

Solutions

Every way AceMQ works with WebLogic.

AceMQ covers WebLogic end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed WebLogic on your infrastructure and fully managed WebLogic on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move WebLogic

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

Stay on WebLogic, or move to Tomcat, WildFly or JBoss EAP, or Payara: what carries over?

Staying and moving are both reasonable, and AceMQ works with WebLogic and with each target below. This table compares what each option carries over from a WebLogic application, not which is better. Open Liberty is the fourth target AceMQ assesses; it is not a column because Liberty is built up feature by feature, so the comparison depends on the features you switch on.

WebLogic, Tomcat, WildFly or JBoss EAP, and Payara compared on Jakarta EE namespace, what carries over, clustering and messaging, support and lifecycle, and fit
QuestionStay on WebLogicTomcatWildFly or JBoss EAPPayara
Which namespace does it use?WebLogic 14.1.2 implements Jakarta EE 8 (the javax namespace). WebLogic 15.1.1 implements Jakarta EE 9.1 (the jakarta namespace), per Oracle's release notes.Tomcat 9.0 uses javax (Servlet 4.0). Tomcat 10.1 (Servlet 6.0) and 11.0 (Servlet 6.1) use jakarta.Current WildFly and JBoss EAP 8 releases use the jakarta namespace.Payara 7 implements Jakarta EE 11, so it uses jakarta.
What does it carry over from WebLogic?Everything. Nothing moves, and the Oracle-specific APIs and descriptors keep working.Servlets, JSP and WebSocket. EJB, JMS and a JTA transaction manager are not part of Tomcat, so an application that uses them needs libraries added or a different target.A full Jakarta EE platform with EJB, JTA and embedded messaging. WebLogic descriptors and APIs still need mapping.A full Jakarta EE platform from the GlassFish line. WebLogic descriptors and APIs still need mapping.
What happens to clustering and JMS?Cluster membership, session replication and WebLogic JMS servers and stores stay as they are.Session clustering exists but works differently. JMS moves to an external broker such as ActiveMQ Artemis or RabbitMQ.High-availability profiles replace WebLogic clusters, and messaging runs on the embedded or an external Artemis broker.Clustering is Hazelcast-based. Which JMS provider to use is a decision for the destinations you have.
Who supports it, and until when?Oracle. Premier Support: 12.2.x to December 2026, 14.1.x to December 2030. Extended Support, a paid add-on, runs to December 2027 and December 2033. Patches need an Oracle contract.The Apache project. Support for 9.0 is expected no earlier than 31 March 2027; 10.1 and 11.0 have no end date stated. AceMQ supports Tomcat directly.WildFly is a community project. JBoss EAP is Red Hat's subscription product, with its dates on Red Hat's policy pages.Payara Community is open source. Supported editions are sold under the Azul Payara name.
When does it fit?The application leans on WebLogic features, and you are content with the support position on your release.Mostly servlets, with transactions and messaging already outside the server.EJB, JTA and JMS-heavy applications that need a Jakarta EE platform.Applications that follow the Jakarta EE specifications closely.

For Tomcat's own support dates, read Tomcat end of life: dates and options.

Not sure which option fits? A senior WebLogic engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

WebLogic rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

FAQs

WebLogic Questions Answered

Five answers on WebLogic from AceMQ: what AceMQ is and is not next to Oracle, which releases are covered, what a platform migration includes, whether your code has to change, and how support works during a migration.

Still have questions about WebLogic? Email an Expert

Is this Oracle support, and does AceMQ provide WebLogic patches?

No. AceMQ is independent of Oracle. Patches and Critical Patch Updates for WebLogic need an Oracle support contract, and AceMQ produces none. AceMQ supplies the engineers who run, troubleshoot and patch your domains, alongside Oracle Support. AceMQ does not offer a cheaper replacement for Oracle's support fee and gives no Oracle licensing advice.

Which WebLogic releases does AceMQ cover?

WebLogic Server 12.2.1.4, 14.1.2 and 15.1.1. Oracle's Fusion Middleware policy (effective 13 April 2026) ends Premier Support for the 12.2.x line in December 2026 and for 14.1.x in December 2030, with paid Extended Support to December 2027 and December 2033. Older releases such as 12.1.3, whose Extended Support ended in January 2022, are scoped case by case, usually with an upgrade or migration plan.

What does a WebLogic platform migration include?

A read-only inventory of your domains, a written mapping of each data source, JNDI name, JMS destination and descriptor to a target, a rehearsal plan and a cutover with the WebLogic domain kept as the rollback. Targets are Tomcat, WildFly or JBoss EAP, Payara and Open Liberty. Application code changes are not included.

Does our application code have to change?

It depends on the namespace. WebLogic 14.1.2 implements Jakarta EE 8 (javax) and 15.1.1 implements Jakarta EE 9.1 (jakarta). A javax application moving to a jakarta-only server needs code changes, and an application that uses EJB, JMS or JTA needs a target that provides them or libraries added to one that does not. AceMQ lists exactly what the target would force, and the changes themselves are outside AceMQ's scope.

Can AceMQ keep WebLogic running while we migrate?

Yes. A migration usually takes more than one change window, and the WebLogic domains keep serving until the last application has moved. AceMQ can cover them with 24/7 support and response targets from 15 minutes, by plan, during that time, then hand the target server over to your team or cover it as well.

Can we work with AceMQ on WebLogic without a long contract?

Yes. AceMQ works on WebLogic in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.

How much does AceMQ WebLogic support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your WebLogic environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how WebLogic is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Tell Us What You Run. We Quote Within 1 Hour.

A senior AceMQ engineer reviews your WebLogic estate, tells you what cover or migration plan fits, and quotes it. Quote requests are answered within 1 hour.

A senior AceMQ engineer, not a sales queueAbout your WebLogic estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a WebLogic Architect

Get in Touch

Talk to a WebLogic Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.