What does AceMQ Spring support include?

Our Tanzu Spring support covers 24/7 emergency incident response with a 15-minute SLA, root cause analysis on every P1, JVM and throughput tuning, upgrade and migration support, native image and AOT work, and Tanzu Spring Runtime commercial entitlement including backported CVE fixes for end-of-life versions. Every ticket is handled by a named senior Java engineer assigned to your account. There is no tier-1 triage layer and no per-incident charge.

We're on a Spring Boot version that reached end of life. What are our options?

Three, and only one of them is usually reasonable under time pressure. You can upgrade, which is right eventually but rarely achievable in the window an audit finding gives you. You can accept the risk, which most regulated environments cannot. Or you can move that version onto Tanzu Spring Runtime commercial support, which continues to deliver backported security fixes to Spring Boot and Spring Framework branches years past open-source EOL. We arrange the entitlement, apply the patched releases, and then plan the real upgrade on a sane timeline instead of a panicked one.

How fast do you respond to a Spring production outage?

P1 emergencies — services down, requests failing, deployment blocked — get a 15-minute first response with a senior engineer joining a live bridge. P2 critical issues are 1 hour, P3 high-priority 4 hours, and P4 standard questions next business day. These are contractual, not best-effort targets.

Can you help with a Spring Boot 2 to 3 upgrade, including the Jakarta namespace change?

Yes, and we run it in stages rather than as a single cutover. The Jakarta EE namespace move touches every servlet, persistence, and validation import, and the surrounding ecosystem upgrades are usually the harder part. We sequence it as dependency alignment, namespace migration, removed auto-configuration replacement, and behaviour verification, with a working build and a rollback at each step. Where a third-party library has no Jakarta-compatible release we identify that in the assessment rather than at the end.

Do you diagnose memory leaks and performance problems, or just answer configuration questions?

We diagnose. Heap dumps analysed for dominator trees and retained sets, thread dumps correlated against pool metrics, JFR recordings for allocation and pinning, and GC logs read against your latency targets. Most of the hard Spring cases we take are not framework questions at all — they are an unbounded cache, a leaked ThreadLocal, or a connection held across a remote call, and none of those are visible without the dump.

Can you help with our Broadcom Tanzu Spring Runtime licensing and true-up?

Yes. As Broadcom's VMware Expert Advantage Partner of the Year for the Americas, we size Spring Runtime subscriptions against your actual application and core counts, reconcile deployments with purchased entitlements, flag true-up exposure ahead of an audit, and negotiate renewal terms. Licensing quotes come back within 24 hours, and the same engineers advising on your upgrade path advise on what you need to license.

How is AceMQ Spring support priced?

Support is priced as an annual contract based on your application estate, required SLA tier, and coverage hours — not per incident or per ticket. Calling us during an outage never carries a cost decision. Contact us for a quote; we turn them around within 24 hours.

Tanzu Spring Support

24/7 Tanzu Spring Support with a 15-Minute Emergency SLA

AceMQ is Broadcom's VMware Expert Advantage Partner of the Year for the Americas. Our senior Java engineers support Spring Boot in production — pool exhaustion under load, slow heap leaks, upgrades that break on removed auto-config, and AOT builds that fail on reflection. We also broker Tanzu Spring Runtime commercial coverage, which keeps backported CVE fixes flowing to Spring Boot and Spring Framework branches that upstream has already ended.

Senior Tanzu Spring engineers on call right now — 24/7/365

15 min emergency SLA24 /7 global coverage130 + enterprise customers26 + countries served

Available Now

Book a free Consultation.

Prefer to chat first?

Prefer to E-mail?

info@acemq.com

Trusted for mission-critical Tanzu Spring by teams in finance, healthcare, defense, and telecom

Escalation Path

Your first hour of a Tanzu Spring outage

Most vendors publish an SLA number. This is what actually happens, minute by minute, when you page a senior AceMQ engineer.

T+0

You page us

Phone, email, or Slack — any channel reaches the on-call senior engineer directly. No web form, no tier-1 queue.

T+15

Named engineer live

A senior engineer who already knows your environment joins a live bridge. Zero cold-start, no re-explaining your topology.

T+30

Root cause isolated

Direct broker access, log and metric review, and a working hypothesis with a rollback plan before we touch anything.

Post

Written RCA

Documented root cause, the fix applied, and the prevention steps — delivered after every P1, not just when asked.

Response Times

SLA tiers, contractually guaranteed

Every tier reaches a senior Tanzu Spring engineer. There is no tier-1 triage layer to get through.

P1 — Emergency

15 min

Production down, messages not flowing, cluster or broker failure

P2 — Critical

1 hour

Severe degradation, rising error rates, approaching capacity limits

P3 — High

4 hours

Performance issues, configuration problems, non-critical failures

P4 — Standard

Next day

Questions, guidance, best practices, non-urgent improvements

Incident Triage

Tanzu Spring problems we fix every week

These are real symptoms from real Tanzu Spring production environments — and the first thing our engineers check when one comes in.

Symptom you're seeingWhat we check firstTypical resolution

Requests hang under load; thread dumps show everything parked in getConnection

What we check firstHikariCP active, idle, and pending counts plus leak-detection-threshold. Nearly always either a pool sized against a database max_connections ceiling it can't reach, or a connection held across a remote call inside a @Transactional method — one slow downstream dependency then drains the pool.

Typical resolutionUnder 2 hours

Heap climbs over days; a restart 'fixes' it and the cycle repeats

What we check firstHeap histogram and dominator tree from a live snapshot. The usual culprits are an unbounded @Cacheable backing map with no eviction, or a ThreadLocal never cleared on a pooled request thread — both invisible in a load test and obvious in a dominator tree.

Typical resolutionSame day

Application won't start after a Spring Boot upgrade — missing bean or auto-config

What we check firstThe specific auto-configuration that was removed or relocated in the target version, and whether the app still relies on spring.factories rather than AutoConfiguration.imports. Then the effective dependency-managed versions, because a pinned transitive dependency defeats the BOM more often than the migration guide suggests.

Typical resolution1–3 hours

Security scan flags an exposed actuator endpoint — /env, /heapdump, or /threaddump reachable

What we check firstmanagement.endpoints.web.exposure settings, whether management runs on a separate port, and whether the Spring Security filter chain actually covers the management base path. An EndpointRequest matcher omitted from the chain is the common miss.

Typical resolutionUnder 1 hour

Open CVE against a Spring Boot or Spring Framework version that reached end of life

What we check firstYour exact version against the Tanzu Spring Runtime commercial support matrix. Commercially supported branches continue to receive backported CVE fixes years past open-source EOL — which for most regulated environments is a faster and far cheaper path than a forced major upgrade under audit pressure.

Typical resolutionUnder 1 hour

GraalVM native image build fails, or the native binary throws where the JVM build didn't

What we check firstAOT processing output and the generated reflect-config against the code paths that failed. Almost always a library using reflection, dynamic proxies, or resource loading without native hints — the fix is a RuntimeHintsRegistrar, not a framework change.

Typical resolutionSame day

Latency spikes after enabling virtual threads on Boot 3.2+

What we check firstJFR jdk.VirtualThreadPinned events. A virtual thread pinned inside a synchronized block during blocking I/O holds its carrier thread, so a small number of pinned tasks can starve the whole scheduler — the fix is usually a ReentrantLock in one library or one class.

Typical resolution1–3 hours

Resolution times reflect typical Tanzu Spring engagements under an active AceMQ support contract. Every P1 closes with a written root-cause analysis.

Not on the list? Tell us what's breaking

What's Included

Everything in your Tanzu Spring support contract

No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.

Emergency Incident Response

Services degraded, pools exhausted, or a deployment that won't start after an upgrade. A senior Java engineer joins a live bridge within 15 minutes with access to diagnose — not a ticket acknowledgement.

EOL Version & CVE Coverage

Tanzu Spring Runtime keeps backported security fixes coming to Spring Boot and Spring Framework branches long past open-source EOL. We broker that entitlement and pair it with the engineering to apply it, so an audit finding doesn't force a rushed major upgrade.

Root Cause Analysis

Every P1 closes with a written RCA: heap dump or thread dump evidence, what failed, the fix applied, and the configuration or code change that prevents recurrence. Delivered as standard, not on request.

JVM & Throughput Tuning

Heap sizing and GC selection, connection pool and thread pool sizing, startup-time reduction, virtual thread adoption, and WebFlux backpressure — tuned against your traffic profile rather than a blog post's defaults.

Upgrade & Migration Support

Spring Boot 2.x to 3.x including the Jakarta namespace move, Spring Framework 5 to 6, XML to annotation-driven configuration, and AOT or native image adoption — planned in stages with a working rollback at each step.

Broadcom Licensing & Entitlement

As Broadcom's Expert Advantage Partner of the Year, we handle Tanzu Spring Runtime subscription questions alongside the technical ones: entitlement reconciliation, true-up exposure, renewal terms, and quotes inside 24 hours.

Anywhere You Run It

We support Tanzu Spring wherever it's deployed

Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.

Kubernetes & OpenShiftTanzu Platform / Cloud FoundryAWS (EC2, ECS, EKS)Microsoft Azure (AKS)Google Cloud (GKE)VMware vSphere & TanzuBare metal & on-premiseAir-gapped / no outbound accessSpring Boot 2.x (EOL branches)Spring Boot 3.xSpring Framework 5 & 6GraalVM native images

Why AceMQ

What you get that you don't get elsewhere

Broadcom Expert Advantage Partner of the Year

AceMQ holds Broadcom's top VMware partner award for the Americas in 2025. For Spring that matters twice over: an escalation path into Tanzu engineering for genuine framework defects, and direct handling of the Spring Runtime entitlement that keeps your EOL branches patched.

EOL Doesn't Mean Unsupported

Open-source Spring Boot branches go end of life on a schedule that has nothing to do with your change-freeze calendar. Commercial Tanzu Spring Runtime coverage continues backported CVE fixes for years past that date — the single most useful thing most enterprises don't realise they can buy.

Named Engineers, Zero Cold Start

The same senior engineers stay on your account. They know your module layout, your pool settings, and your deployment topology — so a P1 starts with diagnosis instead of you explaining your architecture during an outage.

No Tier-1 Triage Layer

You reach a senior Java engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no escalation approval between you and someone who can read a thread dump.

Genuine Follow-the-Sun Coverage

Engineers across 26+ countries and every time zone. Your 3am deployment failure is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

The Whole Stack, Not Just the Framework

Spring problems are frequently database, broker, or platform problems surfacing through Spring. We diagnose across the JVM, the connection pool, the datastore, the message broker, and the Kubernetes layer — because that is where the root cause usually lives.

FAQ

Tanzu Spring support questions

End of Life Upstream Doesn't Have to Mean End of Support

Whether you need emergency response tonight, a stalled Boot 3 upgrade unblocked, or commercial coverage for an EOL Spring branch, AceMQ staffs every engagement with a named senior Java engineer. Support quotes returned within 24 hours.

Get in Touch

Talk to a Support Expert

Send us a message and we'll follow up within one business day — 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.