Independent WSO2 support

WSO2 Support for API Manager Clusters, Identity Server and Micro Integrator Estates

Last reviewed by Tyler Eastridge

AceMQ supports WSO2 API Manager 3.x and 4.x gateway clusters, Identity Server and Micro Integrator estates 24/7. Most calls start with one of three problems: throttling that does not hold across gateway nodes, token validation that slows under load, or a custom mediator that stops working after an upgrade.

24/7 WSO2 support with response targets from 15 minutes, by plan.

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

Planning a build, upgrade or migration instead? See AceMQ WSO2 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 on WSO2

Problems we meet repeatedly across API Manager, Identity Server and Micro Integrator, paired with the component an engineer inspects first.

Common WSO2 production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Throttling limits allowing more traffic than configuredWhether the gateway nodes are sharing throttle state. With multiple gateways and no shared counting — the traffic manager topic not reaching every node, or nodes falling back to local decisions — each node enforces the policy independently and the aggregate is a multiple of the limit.
Token validation latency climbs sharply under concurrent loadGateway token cache configuration and the key manager round trip. With caching disabled or expiring too aggressively, every request becomes a synchronous introspection call to Identity Server, and its database becomes the bottleneck rather than the gateway.
Integration sequence fails or OOMs on a large messageWhether the sequence builds the full message in memory. Content-aware mediators — XSLT, enrich, payload factory, and content-based routing — force the message to be built, so a streaming pass-through flow becomes a buffered one the moment one of them is added.
Database deadlocks and timeouts on the shared AM or registry DBContention on the shared datasource, then whether API Manager, Identity Server, and the registry are all pointed at one database. Consolidated datasources are convenient at install time and the usual cause of lock contention under production concurrency.
An API published in the publisher is not live on every gatewayArtifact synchronisation between nodes — the deployment mechanism in use and whether every gateway received the artefact. Inconsistent gateway file systems and failed sync events leave some nodes serving a stale or missing API.
Custom mediator or extension stops working after an upgradeThe extension point signature against the new version, and the classpath the artefact is loaded from. Internal APIs and handler interfaces change between major versions, so custom code compiled against the old one fails to load with little in the application log.
Backend calls failing with connection timeouts under normal trafficThe pass-through transport worker pool and socket timeouts against backend response time. A slow backend holds transport threads, and once the pool is saturated unrelated APIs on the same gateway start timing out too.
Users intermittently redirected back to login after authenticatingSession persistence across Identity Server nodes and the load balancer's affinity settings. Without shared session state or sticky routing, a request landing on a different node finds no session and restarts the flow.

Each P1 report names the node, datasource or mediator responsible and what stops it recurring.

Gateways rejecting tokens or an API missing on some nodes? Request a quote and we reply within the hour.

Contact Us

Deployment coverage

Which WSO2 setups does AceMQ support, and who covers what?

WSO2 supports its own products under a subscription. AceMQ works on how your deployment behaves in production, next to that subscription or without one.

SetupWhat AceMQ coversWhat WSO2 coversExcluded
API Manager gateway cluster (3.x and 4.x)Throttling and traffic manager topology, token and gateway caches, artifact sync between nodes, transport worker pools, JVM sizingProduct defects and fixes, under a WSO2 subscriptionBackend services behind the gateway
Identity Server and key managerSession persistence across nodes, token introspection load, user store and datasource health, login redirect loopsProduct defects and fixesYour identity provider or directory
Micro Integrator and Enterprise IntegratorSequence and mediation failures, large-payload and memory problems, connector timeouts, EI to MI movesProduct defects and fixesApplication code behind the endpoints
Shared AM, identity and registry databasesDatasource split, connection pool sizing, lock contention, tables that grow without boundProduct behaviourDatabase engine faults
Custom mediators, handlers and authenticatorsReading and remediating the Java after an upgrade: signatures, classpath, load failuresThe documented extension pointsCode you did not give us access to
Kubernetes, VM and bare-metal deploymentsHelm values, node-to-node sync, load balancer affinity, hybrid and air-gapped layoutsThe published charts and installersCluster and cloud control-plane faults

Support options

WSO2 subscription support vs independent support from AceMQ

WSO2 sells support as a subscription: cases go through its support portal, subscribers receive product updates, and its page describes round-the-clock support for critical issues (wso2.com/support, read 17 Nov 2026; the site now redirects to choreolabs.com, which states that WSO2 is now Choreo Labs). The support policy page that sets response times was not read, so no WSO2 response figure is quoted here.

WSO2 subscription
Independent support from AceMQ
Product defects and updatesOnly WSO2 ships fixes and product updates
Product defects and updatesWe reproduce the defect, give the workaround and work the case with you
Response targetsSet by the WSO2 support policy and your subscription
Response targetsFrom 15 minutes, by plan, 24/7 across Americas, EMEA and APAC
Who runs the estateProduct guidance through cases
Who runs the estateNamed engineers who learn your clusters, datasources and custom extensions
PriceSet by WSO2 per subscription
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment
Where AceMQ is not the right fitYou need a product patch or a WSO2 subscription: both come from WSO2 only
Where AceMQ is not the right fit

What's Included

Everything in your WSO2 support contract

API Manager, Identity Server, Enterprise Integrator and Micro Integrator, including clusters where the four share datasources, under one agreement.

  • 01

    Emergency Incident Response

    Gateways failing, tokens rejected, integrations stalled, or a database under lock contention. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the configuration, datasource, or clustering change that prevents recurrence. Delivered as standard, not on request.

  • 03

    Performance & JVM Tuning

    Pass-through transport worker pools, socket and connection timeouts, token and gateway caches, JVM heap and GC settings, and mediation flows profiled against real payload sizes and concurrency.

  • 04

    Clustering & High Availability

    Gateway node synchronisation, traffic manager topology, session replication for Identity Server, artefact deployment consistency, and load balancer configuration that matches the clustering model.

  • 05

    Datasource & Registry Health

    Splitting consolidated datasources, connection pool sizing, registry mounting strategy, index and query tuning on the AM and identity databases, and cleanup of the tables that grow without bound.

  • 06

    Upgrades & Migration Support

    Version upgrades with custom mediator and extension point remediation, moves from Enterprise Integrator to Micro Integrator, and upgrade sequencing for estates that run API Manager, Identity Server and Micro Integrator together.

Why AceMQ

Why integration teams bring WSO2 to us

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your cluster topology, your datasource layout, and your custom extensions — so a P1 call starts with diagnosis, not twenty minutes of you explaining your deployment.

  • No First-Line Triage Layer

    You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass along, and no escalation approval standing between you and someone who can actually fix it.

  • We Treat the Database as Part of the Product

    A large share of WSO2 incidents are really database incidents — shared datasources, lock contention, and tables that grow forever. We work at that layer rather than filing it under someone else's remit.

  • Comfortable in Custom Extension Code

    WSO2 estates accumulate custom mediators, handlers, and authenticators, and upgrades break them. We read and remediate that Java rather than telling you to remove it and lose the behaviour it provides.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

WSO2 clusters we work on

Gateway and key manager clusters on VMs or Kubernetes, multi-datacenter layouts, and sites cut off from outbound internet.

  • WSO2 API Manager 3.x & 4.x
  • WSO2 Identity Server
  • WSO2 Enterprise Integrator
  • WSO2 Micro Integrator
  • Choreo-connected deployments
  • Kubernetes & OpenShift
  • AWS (EC2, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Hybrid & multi-datacentre clusters

Version coverage

WSO2 versions we support

WSO2 lists each release with a support status. The rows below are the releases WSO2 lists as Available or Deprecated on its support matrix, read 17 Nov 2026 (wso2.com/products/support-matrix). WSO2 says each version is supported for at least three years from release, and release lines introduced from March 2024 for at least seven. Running another release? Send it with your quote request and we will say what we can cover.

WSO2 versions we support
ProductReleases we supportWSO2 status
API Manager4.7 (29 Apr 2026), 4.6 (4 Nov 2025), 4.5 (18 Mar 2025), 4.4 (5 Nov 2024), 4.3 (10 Apr 2024), 4.1 (11 Apr 2022)Available
API Manager4.2 (22 Mar 2023)Deprecated: support continues, no new subscriptions
Identity Server7.3 (12 May 2026), 7.2 (24 Oct 2025), 7.1 (11 Mar 2025), 7.0 (4 Mar 2024)Available
Identity Server6.1 (1 Feb 2023), 5.11 (3 Dec 2020)Deprecated
Micro Integrator4.7 (19 Oct 2026), 4.6 (19 May 2026), 4.5 (31 Oct 2025), 4.4 (20 Feb 2025), 4.3 (25 Jul 2024), 4.1 (11 Apr 2022)Available
Micro Integrator4.2 (22 Mar 2023)Deprecated
Enterprise Integrator and older linesThe release you run, on requestNot shown on this list

Source: WSO2 support matrix and support policy, read 17 Nov 2026. Statuses are WSO2's. Response targets from AceMQ, by plan: from 15 minutes for emergencies, 1 hour for critical issues, 4 hours for high-priority issues and the next business day for standard questions.

Escalation Path

Your first hour of a WSO2 outage

A gateway rejecting valid tokens stops every API consumer at once, so that class of incident gets the shortest clock.

  1. From 15 min (by plan)first responseEmergencyGateways unable to validate tokens, the key manager unreachable, or a node cluster that will not start after a change
  2. 1 hourfirst responseCriticalThrottle limits not shared across gateways, database deadlocks on the shared datasource, integration sequences running out of memory
  3. 4 hoursfirst responseHighCustom mediator broken by an upgrade, an API live on some gateways but not others, login redirect loops on Identity Server
  4. Next Dayfirst responseStandardToken cache tuning, database separation plan, version upgrade path, mediator design review

Clocks differ by plan and severity: an outage on every gateway is handled long before a mediator design question.

Want a WSO2 engineer who knows your cluster layout and extensions? Request a quote or write to us.

Contact Us

Pricing

What does AceMQ WSO2 support cost?

WSO2 support typically runs $24,000–72,000 a year. The figure depends on which products you run, how many gateway, traffic manager and key manager nodes there are, how much custom mediator code you maintain, and your response level.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests receive an answer within 1 hour.

Support In Practice

WSO2 incidents we have closed

WSO2 support and remediation work from AceMQ. Each card links to the full write-up: the platform, what AceMQ diagnosed or changed, and the result.

1 / 5 case studies

All use cases

Support options

Four tiers of WSO2 support.

AceMQ offers WSO2 support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for the platform your team runs, proactive monitoring that finds throttling, datasource and keystore problems first, managed WSO2 on your own infrastructure, and fully managed WSO2 on AceMQ infrastructure. API Manager, Identity Server and the integrators are covered.

  • Tier 1

    WSO2 24/7 Support & Incident Management

    Your team runs WSO2, we back it up

    Best for: API platform groups that own their gateways and want a senior engineer for outages and strange token behavior.

  • Tier 2

    WSO2 24/7 Support with Proactive Monitoring

    Scheduled cluster, datasource and mediator reviews

    Best for: Teams who keep finding throttling, session or deadlock trouble in production instead of in a review.

  • Tier 3

    Managed WSO2 on Your Infrastructure

    We operate WSO2 nodes in your datacenter

    Best for: Organizations that must keep gateways, key manager and identity servers on their own infrastructure.

  • Tier 4

    Fully Managed WSO2 on AceMQ Infrastructure

    We run your WSO2 deployment as a service

    Best for: Companies that need API management and identity working without staffing WSO2 specialists.

FAQ

WSO2 support questions

Still have questions about WSO2? Email an Expert

Who provides enterprise support for WSO2?

WSO2 supports its own products under a subscription, with cases raised through its support portal. Independent providers such as AceMQ add 24/7 operational support for gateway clusters, Identity Server and Micro Integrator estates. AceMQ costs $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

Which WSO2 products do you support?

API Manager, Identity Server, Enterprise Integrator and Micro Integrator, alone or together. Mixed estates matter most, because the products often share a database and a deployment pipeline, and a fault in one shows up as a symptom in another.

Why is our throttling not enforcing consistently across gateway nodes?

Usually because the nodes decide independently. Throttle decisions travel through the traffic manager, and if that event path does not reach every gateway, each node enforces limits locally and the total grows with node count. We check traffic manager connectivity from each node first.

Our upgrade broke a custom mediator. Can you fix it?

Yes. Extension interfaces change between major versions, so mediators, handlers and authenticators compiled against the old release can fail to load with little in the log. We read the code, find the changed signatures, remediate against the new version and re-test.

We keep hitting database deadlocks. Is that a WSO2 defect?

Usually not. API Manager, Identity Server and the registry often share one datasource that was fine at install and became a contention point under production concurrency. Splitting datasources, sizing pools and cleaning growing tables fixes most cases.

Why does token validation slow down under load?

With gateway token caching off or expiring too fast, every request becomes a call to the key manager, and its database becomes the bottleneck. Check cache settings and the key manager round trip before adding nodes.

Should we keep a WSO2 subscription if we hire independent support?

Keep it if you need product fixes or updates: only WSO2 provides them. What a subscription does not give you is an engineer who runs your cluster, datasources and custom mediators day to day. Many estates use both.

Who offers WSO2 consulting and professional services?

AceMQ offers WSO2 consulting as named deliverables: a platform assessment, written findings and a plan, implementation alongside your team, and handover with optional cover. See /wso2/.

How fast will you respond to a WSO2 incident?

Response targets start at 15 minutes, by plan, 24/7. Quote replies come within 1 hour.

Can we engage AceMQ on WSO2 for a single upgrade?

Yes. An upgrade with broken extensions, a datasource separation or a gateway cluster review can be scoped alone. A full-year agreement adds 24/7 cover and named engineers, and many teams switch to it after their first project because the engineers already know the cluster.

What determines the price of WSO2 support from AceMQ?

Yearly contracts run $24,000 to $72,000 (USD). The main inputs are which WSO2 products you operate, node counts across gateway, traffic manager and key manager roles, the amount of custom mediator and handler code, and the response target. Send your topology and a quote returns within 1 hour.

Let's talk

Stabilise Your API and Identity Layer

Send your WSO2 product and version, the number of gateway nodes and one throttling or token error. We reply to quote requests within 1 hour.

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

Production incident right now?Email a WSO2 Architect