Who provides enterprise support for Azure Service Bus?
Microsoft supports the Azure Service Bus service under its Azure support plans. Independent providers such as AceMQ support how you use it: entity design, lock and prefetch settings, throttling, dead-letter handling, tier choice and client code behaviour. AceMQ works 24/7 with response targets from 15 minutes, by plan, and a senior engineer assigned to your account on every ticket. Many estates hold both.
What does 24/7 Azure Service Bus support cover with AceMQ?
It covers round-the-clock incident response, a written root cause on every P1, and standing work such as lock and delivery count reviews, quota checks and Geo-DR rehearsals. A Sev 1 like a namespace throttling every send starts within 15 minutes on the top plans.
Why are our Service Bus messages processed twice?
In PeekLock mode a message is locked for the lock duration. If the handler runs longer and the lock is not renewed, the message is delivered again and completing the first copy fails with MessageLockLostException. Large prefetch counts make it worse because locks start before handling does. We set lock duration and auto-renewal from measured handler time and make handlers idempotent.
How do we fix ServerBusyException on Azure Service Bus?
First find which tier you are on. Basic and Standard throttle on a credit model with a published 1,000 operations per second. Premium throttles on CPU and memory of the allocated messaging units. We read the throttled-request metrics against traffic, then batch sends, reuse clients and trim filters, or resize Premium. Moving tier is a measured decision, not a reflex.
Should we use Standard or Premium?
Premium gives isolated resources, predictable throughput, messages up to 100 MB over AMQP, JMS 2.0, Geo-DR and private-link features. Standard is shared and throttles. Choose Premium for production workloads with burst, size or isolation needs. We size it from your peak rate, message size, subscription count and filter complexity, so you pay for the units you need.
Why is our dead-letter queue filling with no application errors?
Read the dead-letter reason. MaxDeliveryCountExceeded means the message was delivered the maximum number of times (10 by default) without completing. TTLExpiredException means the message expired before a consumer received it. Other reasons are filter action errors and header size. Each points to a different fix, and we write a replay procedure so recovery does not flood the live entity.
What happens to messages during an Azure Service Bus Geo-DR failover?
Geo-disaster recovery pairs Premium namespaces behind an alias and fails the alias over. It replicates entity metadata, not the messages waiting in the primary, so you plan for unprocessed work and for clients that still hold the old connection string. We rehearse the failover before you need it.
Can AceMQ help us migrate onto or off Azure Service Bus?
Yes. We support both directions, using patterns such as bridged queues and dual consumption so cutover is reversible. We have worked on Service Bus to RabbitMQ migrations for financial services and banking clients, and on Service Bus cost reviews. See the linked use cases.
Does Azure Service Bus support JMS?
Yes, on Premium, which offers JMS 2.0 over AMQP. Java and Spring applications can then use Service Bus through standard JMS interfaces, and we help with connection factory settings, transactions and redelivery behavior.
Where does AceMQ support end and Microsoft support begin?
Microsoft runs the platform: availability, capacity, quotas and confirmed service defects. AceMQ works on your side of the line: entity design, client settings, lock handling, filters and diagnosing why a message behaved as it did.
Is a multi-year or annual commitment required for Service Bus help?
No. A throttling investigation, a dead-letter and lock review, a Geo-DR failover rehearsal or a migration plan can each be scoped as a separate job. If messaging incidents continue, an annual agreement adds 24/7 response and engineers who know your namespaces.
What affects the cost of Azure Service Bus support?
Annual plans run $24,000 to $72,000 (USD). We look at namespace count, Standard or Premium tier, messaging units, how many queues and topics carry production traffic, and the response level. Microsoft's service charges are separate. Describe the setup and a quote returns within 1 hour.