Application framework support

Tanzu Spring Support for Spring Boot, Framework and Cloud Estates

Last reviewed by Tyler Eastridge

AceMQ supports Spring Boot, Spring Framework and Spring Cloud 24/7 across Americas, EMEA and APAC on Kubernetes, OpenShift, Tanzu Platform and virtual machines, alongside Broadcom's Tanzu Spring subscription where you hold one. Most calls start with one of three problems: pods failing health probes or dropping requests on deploy, connection pools exhausted under load, or a Spring Boot upgrade that will not start.

AceMQ is Broadcom's 2025 Tanzu Partner of the Year, a Leading Broadcom Tanzu partner and a Leading Global Services Partner. 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. Response targets from 15 minutes, by plan; quote replies within 1 hour.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Spring consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Eight Spring Boot production problems, each with the Actuator endpoint, Micrometer metric or JVM command we use before editing configuration.

Common Spring production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Pods fail readiness or restart in a loop on KubernetesWe check management.endpoint.health.probes.enabled, the /actuator/health/liveness and /readiness groups, and which health indicators sit in each group. A database check inside the liveness group restarts every pod when the database blips. The startup actuator endpoint (with BufferingApplicationStartup) shows which bean slows startup so the probe initialDelaySeconds or a startup probe is set from data.
Requests fail with 502 or 503 during every deployThe cause is usually shutdown order. We compare server.shutdown=graceful and spring.lifecycle.timeout-per-shutdown-phase with the pod's terminationGracePeriodSeconds and a preStop delay, so the load balancer stops sending traffic before the application stops accepting it.
Connection pool exhaustion under loadWe read hikaricp_connections_active, hikaricp_connections_pending and hikaricp_connections_timeout_total from Micrometer, take two thread dumps with jcmd <pid> Thread.print to see where threads wait, and size maximum-pool-size against the database max_connections multiplied by replica count.
Out-of-memory kills with a healthy heapThe container limit includes metaspace, thread stacks and native memory. We set -XX:MaxRAMPercentage, switch on -XX:NativeMemoryTracking=summary, and read jcmd <pid> VM.native_memory summary before changing the limit.
A Spring Boot upgrade will not startWe run spring-boot-properties-migrator to list renamed properties, check removed auto-configuration, and sequence the work: dependency alignment first, then the Jakarta namespace change, then Hibernate and Spring Security changes. Broadcom's Application Advisor and OpenRewrite recipes automate the mechanical part; the tests and the data layer need people.
Spring Security returns 403 or 401 after a changeWe turn on logging.level.org.springframework.security=DEBUG, read the filter chain order for each SecurityFilterChain bean, and check CSRF, CORS and path matcher changes. A POST that returns 403 behind a gateway is CSRF until proven otherwise.
Spring Cloud Gateway latency or Config Server driftFor Gateway, we check the Reactor Netty connection pool (spring.cloud.gateway.httpclient.pool.*) and blocking calls on event-loop threads. For Config Server, we check spring.config.import, refresh behaviour through /actuator/refresh and which instances still hold old values.
Metrics cost more than the applicationMicrometer URI tags with path variables create a series per ID. We set management.metrics.web.server.max-uri-tags, fix route templates, and drop tags that carry user data, which also cuts the load on Prometheus.

After each P1 we send a short analysis naming the property, probe or dependency that produced the failure.

Pods restarting every deploy and customers seeing 503s? Request a quote and a Spring engineer replies within an hour.

Contact Us

Deployment coverage

Which Spring estates does AceMQ support, and who covers what?

EstateWhat AceMQ coversWhat the vendor coversExcluded
Spring Boot and Framework on Kubernetes or OpenShiftApplication and runtime incidents, probes, shutdown, pools, JVM, security configuration, upgradesThe platform vendor supports the clusterControl-plane faults
Tanzu Platform and Cloud FoundryApplication-level incidents and tuning; escalation with Broadcom for platform defectsBroadcom supports Tanzu PlatformPlatform defects stay with Broadcom
Spring on virtual machines and bare metalThe same application scope, plus JVM and OS-level tuningNo vendor unless you hold a Spring subscriptionHardware and OS faults outside the agreed scope
Spring Cloud Gateway, Config Server and Service RegistryRouting, filters, configuration refresh, discovery behaviourBroadcom lists these among the products its Spring subscription supports (enterprise.spring.io, read 17 Nov 2026)Product defects stay with Broadcom
Spring Boot native images (GraalVM)AOT output and reflection hints, build failures, parity with the JVM buildBroadcom supports OpenJDK and Spring under its subscriptionThird-party libraries that do not support native builds

Better together

Broadcom subscription plus AceMQ engineers: how Tanzu Spring support fits together

Broadcom owns the Spring portfolio and sells an enterprise Spring subscription. AceMQ sits beside it and covers the application behaviour a subscription does not fix, in the same estate.

Broadcom subscriptionAceMQ engineers alongside it
What it coversOver 50 Spring projects, plus OpenJDK and Tomcat, with 24x7 global support (enterprise.spring.io, read 17 Nov 2026)Your applications and runtime: Boot, Framework, Cloud, the JVM, Tomcat and Kubernetes behaviour
Hours and responsePer the terms of your subscription, which state fast response times24/7 across Americas, EMEA and APAC; response targets from 15 minutes, by plan
PatchesDay 0 access to patches for enterprise versions and the latest open-source releasesWe diagnose on any version and advise on exposure and upgrade order
Root cause analysisPer Broadcom's processWritten root cause analysis on every P1
Product defectsShips patches for the versions in the subscriptionWe diagnose, gather the evidence and work the escalation with you
PriceSet by the Broadcom subscription$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

If you need the commercial features, the entitlement or the fixed builds, you buy them from Broadcom. If you also want senior engineers on call across time zones, that is a separate contract that sits beside it. Many estates do both, and AceMQ is a Leading Global Services Partner for Broadcom.

Something changed?

Renewal under Broadcom's model? Start here

Each guide says what changed, who it affects and what to decide first.

What's Included

Everything in your Spring support contract

Spring Boot services, Spring Security, Spring Cloud Gateway, Config Server and the JVM beneath them are handled together, with no separate fee per incident.

  • 01

    Emergency Incident Response

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

  • 02

    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.

  • 03

    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.

  • 04

    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.

  • 05

    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.

  • 06

    Broadcom Licensing & Entitlement

    As Broadcom's 2025 Tanzu 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.

Why AceMQ

Why Spring teams add a second set of engineers

  • Broadcom's 2025 Tanzu 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

    Round-the-clock coverage for customers in 26+ countries. 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.

Where Spring runs under our support

Spring workloads on Kubernetes, OpenShift and Tanzu Platform, on AWS, Azure or Google Cloud, on vSphere, and on hosts with no outbound access.

  • Kubernetes & OpenShift
  • Tanzu Platform / Cloud Foundry
  • AWS (EC2, ECS, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • VMware vSphere & Tanzu
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Spring Boot 2.x (EOL branches)
  • Spring Boot 3.x
  • Spring Framework 5 & 6
  • GraalVM native images

Version coverage

Versions we support

Versions we support
Spring Boot lineStatusNote
4.1Current release on spring.io: 4.1.2spring.io/projects/spring-boot, read 17 Nov 2026
3.xSupported in productionUpgrade path planned from your minor
2.7 and earlier 2.xSupported in productionSpring Framework 5.3.x follows the matching Boot line

Escalation Path

Your first hour of a Spring outage

The engineer on the call has read a thread dump and an Actuator health group before, so diagnosis starts with the pod, the pool or the filter chain.

  1. From 15 min (by plan)first responseEmergencyProduction outage: pods in a restart loop, every request failing with 502 or 503, services unable to start after a release
  2. 1 hourfirst responseCriticalSevere degradation: HikariCP pool exhausted, containers killed for memory while the heap looks healthy, a Security change returning 403 everywhere
  3. 4 hoursfirst responseHighErrors during each rolling deploy, Config Server drift, Gateway latency from blocking calls on event-loop threads
  4. Next Dayfirst responseStandardQuestions on probe design, pool sizing, Micrometer cost, Boot version sequencing and GraalVM native images

Targets depend on plan: pods failing readiness in production and a question about Boot upgrades are not queued together.

Prefer named engineers who already know your services and probes? Ask for a quote or book a call.

Contact Us

Pricing

What does AceMQ Spring support cost?

Spring support usually costs $24,000–72,000 a year. The number of services and replicas, whether you use Gateway and Config Server, the platform they run on, and the response plan decide where a contract falls.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and we answer quote requests within 1 hour. Contracts that include other technologies carry a multi-technology discount.

Support In Practice

Spring Boot failures we have diagnosed

Spring support and upgrade work from AceMQ. Each card links to the full write-up: the application estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

  • CVE Patching

    Day-Zero Spring CVE Patching for Retail and Banking Enterprises

    Enterprise Retail and Banking Organizations

    AceMQ provides day-zero CVE patch access for Spring Framework through Broadcom's commercial Spring subscription, enabling retail and banking organizations to address critical Spring security vulnerabilities immediately upon disclosure.

    Spring Framework
  • CVE Patching

    Spring Framework Compliance and Security Patching for Government

    Government and Public Sector Agencies

    AceMQ delivers Spring Framework security compliance programs for government agencies, meeting 48-hour critical patch SLA requirements through Broadcom commercial Spring support with FIPS compliance and audit documentation.

    Spring Framework
  • Assessment

    Managing Spring Framework CVE Risk at Enterprise Scale

    Enterprise Software Organizations

    AceMQ helps enterprise software organizations quantify and manage the CVE risk exposure created by running community Spring Framework without a commercial support agreement, transitioning them to Broadcom commercial support.

    Spring Framework
  • Assessment

    GemFire Cluster and Region Architecture Assessment

    Enterprise Technology Organizations

    A structured review of GemFire region design, WAN topology, JVM tuning and security configuration, producing a risk-prioritized roadmap before problems reach production.

    GemFireJavaSpring
  • Support

    Unblocking Producers on an ActiveMQ Classic Broker Pair

    Regional Payments Processor

    Four live sessions to find why every producer on an ActiveMQ Classic 5.16 pair stalled when one settlement consumer slowed, and to give each destination its own memory limit.

    ActiveMQSpring FrameworkJavaLinux
All use cases

Support options

Four tiers of Spring support.

AceMQ offers Spring support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for services your team runs, proactive monitoring that catches pool, heap and end-of-support problems first, managed Spring operations on your own infrastructure, and fully managed Spring platform services on AceMQ infrastructure. Spring Boot 2.x and 3.x are covered in all four.

  • Tier 1

    Spring 24/7 Support & Incident Management

    Your developers own the services, we take escalations

    Best for: Teams shipping Spring Boot themselves who want a senior engineer for probe, pool and memory problems they have not solved.

  • Tier 2

    Spring 24/7 Support with Proactive Monitoring

    Reviews of probes, pools and JVM settings

    Best for: Teams that meet shutdown errors, pool timeouts and container memory kills in production before they meet them in review.

  • Tier 3

    Managed Spring on Your Infrastructure

    We run your Spring services on your platform

    Best for: Organizations with Kubernetes, OpenShift or Tanzu Platform that must stay in their own accounts and want specialists operating Spring.

  • Tier 4

    Fully Managed Spring on AceMQ Infrastructure

    AceMQ operates your Spring services as a service

    Best for: Product teams that want services kept stable and upgraded without a dedicated platform and JVM team.

FAQ

Spring support questions

Still have questions about Spring? Email an Expert

Who provides enterprise support for Spring Boot?

Broadcom sells an enterprise Spring subscription covering over 50 Spring projects, OpenJDK and Tomcat. For the application behaviour a subscription does not fix, and for estates without one, AceMQ provides 24/7 support with response targets from 15 minutes, by plan.

Why do our pods restart when the database is slow?

The database health indicator is probably in the liveness group. Move it to readiness, so traffic stops but pods are not killed.

Why do we see errors on every deployment?

The pod stops before the load balancer drains it. Set graceful shutdown, align the phase timeout with the pod's termination grace period, and add a short preStop delay.

How do we size HikariCP?

Start from the database connection ceiling divided by the replica count at peak, then confirm with hikaricp_connections_pending under load. Bigger pools often make databases slower.

What is the safest way to upgrade Spring Boot?

One minor at a time on the 2.x line up to 2.7, then 3.x, with the properties migrator and a green test suite at each step. The Jakarta namespace move is the largest single change.

Do you help with Spring Cloud Gateway and Config Server?

Yes. For Gateway we look at routes, filters and Reactor Netty pool settings, and for Config Server we check spring.config.import and how configuration refresh reaches running services.

What does a Spring health check include?

We read probe groups and shutdown behavior, pool and thread settings, JVM and container sizing, actuator exposure, Spring Security configuration and Micrometer tag cardinality, then return a prioritized list with the property or code change for each item.

Can you support Spring alongside Tomcat and the JVM?

Yes, under one contract. See /tomcat/support/ and /java/support/.

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.

Do we need a yearly contract to get Spring help?

No. A shutdown and probe review, a HikariCP and thread dump investigation, a Boot upgrade plan or a security filter chain audit can each be bought as defined work. Teams that call repeatedly usually choose an annual agreement with 24/7 response.

How much does Spring support cost and what moves the price?

Plans range from $24,000 to $72,000 a year (USD). The quote reflects how many Spring Boot services and replicas you run, whether Cloud Gateway and Config Server are part of the estate, which platform hosts them, and the response level. Send a short description and we answer within 1 hour.

Let's talk

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

Send us the Spring Boot version, the Kubernetes manifest and the last thread dump. We reply within 1 business hour with the first thing we would change.

A senior Spring engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a Spring Architect