Solace support, 24/7

Solace Support for Software Brokers, Appliances, HA Pairs and Event Mesh Estates

AceMQ supports Solace 24/7 on software brokers, appliances and event mesh estates, beside your Solace plan or on its own. Most calls start with one of three problems: a message spool filling because one queue has no consumer, an HA pair that did not fail over cleanly, or a slow subscriber backing up a whole message VPN.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

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

min fastest response target, by plan
15
across Americas, EMEA, APAC
24/7
enterprise customers
160+
Sev 1 incidents handled a year
40+

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

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Solace problems we fix every week

Spool, HA, redelivery and event mesh problems on Solace brokers, each paired with the broker statistic or log an engineer reads first.

Common Solace production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Publishers rejected or slowed, message spool usage near its quotaPer-queue spool usage and the queue with no active consumer (show message-spool detail, show queue <name> detail); queues with no maximum spool usage set; messages waiting on a consumer that was decommissioned.Bound each queue's maximum spool usage, remove or drain the orphan queue, add a dead message queue and a TTL where the data allows it.
One slow subscriber stalls delivery to others on the same message VPNFlow state for the client (show client <name> detail), unacknowledged messages against the queue's max-delivered-unacked-msgs-per-flow, the client's window size, and the queue depth behind the flow.Fix the consumer's acknowledgement pattern, size the window for the round trip, set a spool limit so one consumer cannot fill the broker.
HA pair failed over but clients did not reconnect, or the pair will not stay in syncshow redundancy and show config-sync on both nodes and the monitoring node; whether the redundancy link is up; whether the client's reconnect settings match the measured failover time.Repair the link or the config-sync state, correct reconnect retries and timeouts in the client, rehearse a planned switchover.
Messages redelivered in a loop to the same consumerThe queue's max-redelivery setting (zero means retry forever), the consumer's processing errors, and whether a poison message is blocking an exclusive queue.Set a maximum redelivery count with a dead message queue, quarantine and inspect the poison message, fix the consumer.
Event mesh link between two brokers is down or laggingDynamic message routing link state and the bridge queue depth between the brokers; certificate or network changes on the inter-broker path; subscription propagation.Restore the link, correct the TLS chain, validate subscription propagation, check the receiving side's spool.
Client connections refused after growthMessage VPN and broker limits for connections and subscriptions (max-connections, max-subscriptions); client profile and ACL profile rules for the new application.Raise the limit that is actually reached, correct the profile rules, set per-VPN limits so one team cannot consume the broker.
Disk or spool filling after a replay or a large backlogReplay log size and retention, spool pressure while the backlog drains, and whether consumers were scaled for catch-up.Size replay and spool for the drain rate, throttle the replay, add consumers for catch-up.

Every P1 comes with a written cause naming the queue, message VPN or link involved.

Publishers being rejected or an HA pair misbehaving? Ask for a quote and a Solace engineer replies within the hour.

Contact Us

Deployment coverage

Which Solace deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat Solace coversExcluded
Software event brokers on virtual machines and containers24/7 incident response, message spool and queue design, client profile and ACL profile review, HA pair behavior, upgrades, written RCA on P1sSolace supplies releases and fixes for the software and takes product defect cases (solace.com/support, read 17 November 2026)A patched Solace binary
Appliance event brokersConfiguration, queue and spool behavior, HA pair operation and upgrade rehearsal on the appliance brokerReturn Material Authorization and hardware sparing or repair, as its support plan describesHardware faults and replacement
Event mesh and dynamic message routing between brokersLink design, subscription propagation checks, inter-broker TLS, bridge queue sizing, failure drills across sitesSolace supports the product features it shipsNetwork paths between your sites
Solace CloudThe application and configuration layer you control: queues, topics, client behavior, ACLsSolace operates its cloud service and supports it through its own console and planService-level faults
Replication and disaster recovery sitesReplication state checks, failover drills, runbooks that are testedSolace supports the productStorage and WAN faults
Clients and APIs (Java, JMS, .NET, C, Python, JavaScript, MQTT, AMQP)Reconnect behavior, acknowledgement patterns, flow control, protocol mappingSolace supports its own APIsApplication code defects

Solace and independent support

Who provides enterprise support for Solace? Solace and independent support compared

Solace provides enterprise support for its own event brokers through its support plan, with 24/7/365 hours. Independent providers such as AceMQ support Solace operations and troubleshooting alongside that plan or without it. Solace fixes product defects and supplies hardware; an independent contract adds an engineer who works your configuration and your clients.

Solace support plan
AceMQ independent support
What it coversEvent Broker (appliance and software), Solace Cloud, Event Portal, the APIs and supporting software such as Solace Cache (solace.com/support, read 17 November 2026)
What it coversSolace event brokers on software, appliance and cloud deployments, plus the clients, the surrounding estate and any other brokers you run
Hours24/7/365 (solace.com/support, read 17 November 2026)
Hours24/7 across Americas, EMEA and APAC
Severity 1 response30 minutes on Standard Support or Essential Services, 15 minutes on Advanced Services (solace.com/support, read 17 November 2026)
Severity 1 responseFrom 15 minutes, by plan
Severity 2 and 32 hours and next business day (solace.com/support, read 17 November 2026)
Severity 2 and 31 hour and 4 hours, with P4 on the next business day
How a first response is measuredSeverity 1 and 2 are measured only when you contact support by phone (solace.com/support, read 17 November 2026)
How a first response is measuredWe answer on the bridge; written RCA on every P1
Product defects and new releasesSolace supplies the fix and the releases
Product defects and new releasesWe reproduce, open the case with Solace on your behalf and apply the fix
Product questions and operationsSolace answers questions about its products
Product questions and operationsCore of our work: queues, spool, ACLs, HA, mesh links, clients
HardwareA Return Material Authorization is issued first; Rapid Hardware Repair Service carries an additional fee, and spares otherwise ship the next business day from Ottawa (solace.com/support, read 17 November 2026)
HardwareNot in scope; Solace remains the route
Brokers outside SolaceNot in scope
Brokers outside SolaceKafka, IBM MQ, RabbitMQ, ActiveMQ and others under one contract
PriceNot published on the support page (read 17 November 2026)
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

Solace's own Advanced Services target is 15 minutes for Severity 1, and ours starts from 15 minutes by plan, so response time alone is not the reason to add an independent contract. The reason is scope. A spool that fills because nobody owns a queue, or a client that reconnects too slowly after a switchover, is configuration, and an engineer who reads your setup is faster than a defect ticket.

Why AceMQ

What Solace teams gain from AceMQ

On the first call

Reading a Solace incident: the four outputs we ask for

On the first call we ask for four artefacts because they separate causes in minutes.

1. show message-spool detail

From the active broker. It shows total spool use against quota and tells us whether one queue or the whole broker is the problem.

2. show queue <name> detail

For the queue behind the symptom. Depth, consumer count, redelivery settings and the maximum spool size separate an orphan queue from a slow consumer.

3. show redundancy and show config-sync

On both nodes. They show which node is active, whether the link is up and whether the pair agrees on configuration.

4. The client's connection settings

Reconnect retries, the acknowledgement mode and the window size. Most "the broker lost messages" calls end here.

Escalation Path

Your first hour of a Solace outage

A message spool at its quota stops publishers in minutes. The engineer on the line starts with queue depth and consumer binds, not with questions about what Solace is.

  1. From 15 min (by plan)first responseEmergencyProduction outage: publishers rejected, an HA pair split or down, or clients unable to connect to the broker
  2. 1 hourfirst responseCriticalSerious degradation: spool near quota, a slow subscriber holding up delivery, an event mesh link failing
  3. 4 hoursfirst responseHighMessages redelivered in a loop, connection limits hit after growth, disk filling after a replay
  4. Next Dayfirst responseStandardQueue and endpoint design, message VPN limits, upgrade runbooks, health check findings and migration planning

Your plan sets the clock: a full message spool is treated differently from an upgrade planning query.

Want a named Solace engineer who knows your message VPNs and mesh links? Request a quote or contact us.

Contact Us

Pricing

What does AceMQ Solace support cost?

Solace support is usually priced from $24,000 to $72,000 a year. The number of brokers and message VPNs, appliance versus software, event mesh scale and your response plan shape where you fall.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract that also covers other messaging systems earns a discount.

Support options

Four tiers of Solace support.

AceMQ offers Solace support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for brokers your team runs, proactive monitoring that catches spool, HA and mesh drift first, and managed Solace, where AceMQ runs your brokers day to day and quotes the scope per estate. Hardware repair and replacement stay with Solace in every tier.

  • Tier 1

    Solace 24/7 Support & Incident Management

    Your messaging team runs Solace, we assist

    Best for: Teams operating Solace brokers who want an expert reachable for spool, failover or delivery problems.

  • Tier 2

    Solace 24/7 Support with Proactive Monitoring

    Planned reviews of queues, limits and HA health

    Best for: Teams that want spool trends, slow consumers and failover behavior examined before they reach a limit.

  • Tier 3

    Managed Solace on Your Infrastructure

    We operate your Solace brokers in your estate

    Best for: Enterprises that keep brokers on their own sites and want AceMQ running them day to day.

  • Tier 4

    Fully Managed Solace on AceMQ Infrastructure

    AceMQ runs the event mesh for you

    Best for: Teams that need guaranteed messaging without building a specialist team to look after the brokers.

FAQ

Solace support questions

Still have questions about Solace? Email an Expert

Who provides enterprise support for Solace?

Solace provides enterprise support for its event brokers through its support plan, with 24/7/365 hours and a 15-minute Severity 1 target on Advanced Services (solace.com/support, read 17 November 2026). Independent providers such as AceMQ support Solace operations, troubleshooting and incident response beside that plan or on its own, with response targets from 15 minutes, by plan.

Can you support Solace alongside our Solace plan?

Yes, and that is the usual set-up. Solace handles product defects, releases and hardware. We handle why a spool filled, why clients did not reconnect after a switchover and how queues, ACLs and mesh links should be configured. When a defect is involved we open the case with Solace and drive it.

Do you support Solace appliances as well as software brokers?

We support the configuration and operations of both: queues, spool, HA pairs, upgrades and clients. Hardware replacement and repair stay with Solace, whose support plan requires a Return Material Authorization for it (solace.com/support, read 17 November 2026).

Why is my Solace message spool filling?

A spool fills when messages arrive faster than consumers acknowledge them, or when a queue has no active consumer. We check queue depth by endpoint, consumer binds and any large replay, then adjust quotas or the slow consumer. Raising the quota alone only delays the problem.

Why did our HA pair fail over but clients did not follow?

After a failover, clients reconnect only if they list both broker addresses and retry. We check the HA pair's sync state, the client connection URL, reconnect settings and any firewall or DNS pointing at one node, then test the switch in a planned window.

What does a Solace health check include?

Spool and queue sizing, message VPN limits, client and ACL profile review, HA pair and config-sync state, event mesh link and bridge queue state, certificate expiry, replay and replication settings, client reconnect behavior, and a ranked plan. Quotes are answered within 1 hour.

How do you plan a Solace upgrade without downtime?

We start from the release each broker is on, check client and API compatibility, upgrade the backup node first in an HA pair, rehearse a switchover, then upgrade the other node and keep a rollback. The first step is an inventory of broker versions, topology and clients.

Can you help us move from Solace to Kafka, IBM MQ or RabbitMQ, or the other way?

Yes. Solace supports AMQP, Kafka, MQTT, REST and WebSocket (solace.com/products/event-broker, read 17 November 2026), which makes phased moves with parallel running practical. We map topics, queues and delivery guarantees to the target, run both sides side by side and keep a rollback. See Solace consulting.

Is Solace PubSub+ the same as Solace Event Broker?

They refer to the same broker product line. Solace's pages use the name Solace Event Broker and still carry the PubSub+ name in places (solace.com/products/event-broker, read 17 November 2026). We support the deployed broker whichever name your team uses.

Can we use AceMQ for Solace without leaving our current vendor plan?

Yes. Many teams keep their Solace plan and add AceMQ for the gaps, such as spool and HA diagnosis at odd hours, upgrade planning or advice across several messaging platforms. You can also hire us for one project, like a health check, with no annual commitment.

What drives the price of Solace support?

Annual contracts typically run $24,000 to $72,000 (USD). Inputs are broker count, appliance or software form, message VPNs and HA pairs, event mesh links, and your response plan. Describe the estate in a quote request and we respond within 1 hour.

Let's talk

Find the Queue Nobody Is Consuming Before It Fills the Spool

Send us your broker versions, the HA and mesh topology and the queues that carry your critical traffic. We reply to quote requests within 1 hour.

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

Production incident right now?Email a Solace Architect