Which Spring Boot versions are still supported, and until when?
As of 19 October 2026 only Spring Boot 4.0, supported by the open-source project to 31 December 2026, and 4.1, to 31 July 2027, still get free fixes. Boot 3.5 left open-source support on 30 June 2026 but has commercial support to 30 June 2032, and Boot 2.7 has it to 30 June 2029. AceMQ chooses the route for each application.
What are our options when a Spring Boot version reaches end of life?
Three: upgrade, buy commercial support for the line, or use patched builds. Tanzu Spring commercial support covers selected lines for years past open-source end of support, and AceMQ's OSSeva patched builds cover Boot 2.6 to 3.5 through your Maven or Gradle repository. AceMQ matches each application to a route and supports the result.
Who answers when a Spring application fails in production, and how fast?
A named AceMQ senior Java engineer joins a live bridge within 15 minutes, 24/7, when a Spring service is down, pools are exhausted or a deployment will not start. Lower severities get a first response within 1 hour, 4 hours or the next business day. The engineer who takes the call stays on the case, and every P1 ends in a written root-cause analysis.
How does an AceMQ Spring engagement start?
An AceMQ Spring engagement starts with a free consultation with a senior Java engineer, scheduled within 24 hours. An application and dependency assessment of 1 to 2 weeks follows, inventorying Spring Framework and Boot versions, Jakarta and JDK blockers, shared starters, pool sizing and your support position. Written findings arrive within a week.
Can AceMQ help with a Spring Boot 2 to 3 upgrade, including the Jakarta namespace change?
Yes, in stages. Spring Boot 3 needs Java 17 or later and moves javax imports to jakarta, and the surrounding libraries are usually the harder part. AceMQ sequences dependency alignment, namespace migration, removed auto-configuration and behaviour checks, with a working build and a rollback at each step. A library with no Jakarta release is flagged in the assessment.
Why do our Spring Boot pods get killed during startup on Kubernetes?
Because the application takes longer to start than the liveness probe allows. After an upgrade or a schema migration, startup can exceed the probe window, so Kubernetes kills the pod and restarts it in a loop. AceMQ measures the real start time, adds a startup probe, trims the start with lazy initialization or AOT, and moves migrations into their own job.
Why do requests hang under load with threads parked in getConnection?
The HikariCP pool is exhausted: either it is sized beyond what the database allows, or a connection is held across a remote call inside a transactional method, so one slow downstream dependency drains the pool. AceMQ reads the pool's active, idle and pending counts with leak detection, then fixes the pool size or moves the remote call out of the transaction.
How does Tanzu Spring licensing work through AceMQ?
AceMQ sizes a Tanzu Spring subscription against your applications and cores, reconciles it with what you run and handles renewals. Licensing through AceMQ is available to US customers with a 72-core minimum. The engineers who advise on your upgrade path advise on what to license, and quote requests are answered within 1 hour.
Can we work with AceMQ on Spring without a long contract?
Yes. AceMQ works on Spring 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 partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
How much does AceMQ Spring support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your Spring environment, the SLA you need, the hours of cover and the scope of work. We do not send generic quotes or publish a price list, because two estates of the same size rarely need the same thing. Request a quote and AceMQ replies within 1 hour.
RabbitMQ
AWS
