amqp-debug

Analyze AMQP 1.0 frames and Azure SDK compatibility issues in Service Bus emulator logs.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Indomitable/fast-servicebus-emulator --skill amqp-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amqp-debug
Source: https://github.com/Indomitable/fast-servicebus-emulator/tree/main/.agents/skills/amqp-debug
Command: npx skills add https://github.com/Indomitable/fast-servicebus-emulator --skill amqp-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers diagnose and resolve complex issues arising from interactions between the Azure Service Bus emulator and Azure SDKs, specifically focusing on AMQP 1.0 protocol nuances and known compatibility problems.

Core Features & Use Cases

  • Protocol Analysis: Parses AMQP frames from emulator logs to identify violations and inconsistencies.
  • SDK Bug Identification: Checks for and provides workarounds for common Azure SDK bugs impacting Service Bus communication.
  • Message Broker Validation: Verifies message properties, disposition settlements, and flow control mechanisms.
  • Use Case: When your .NET application experiences Nullable object must have a value exceptions during Service Bus message reception, this Skill can analyze emulator logs and SDK source code to pinpoint the header serialization issue and suggest the necessary fix.

Quick Start

Use the amqp-debug skill to analyze emulator logs for initial-delivery-count issues.

Frequently Asked Questions about amqp-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug AMQP 1.0 protocol errors with the Azure Service Bus emulator?

To debug AMQP 1.0 protocol errors, analyze AMQP frames from emulator logs to identify protocol violations and cross-reference them with Azure SDK source code. This process validates message broker properties, disposition settlements, and flow credit mechanisms.

Why does my .NET application throw a 'Nullable object must have a value' exception during Service Bus message reception?

The 'Nullable object must have a value' exception during Service Bus message reception occurs due to a header serialization issue. Analyzing emulator logs and Azure SDK source code pinpoints this specific incompatibility and suggests the necessary workaround.

How do I fix the InitialDeliveryCountIsNone error in my Service Bus emulator?

Fixing the InitialDeliveryCountIsNone error involves cross-referencing emulator logs with Azure SDK source code to identify delivery count mismatches. This validates initial delivery count properties and resolves disposition settlement issues within the AMQP connection.

Can I use this tool to identify known Azure SDK bugs impacting Service Bus communication?

Yes, you can identify known Azure SDK bugs impacting Service Bus communication by checking for specific compatibility problems. The tool analyzes AMQP frames, validates message properties, and provides workarounds for common SDK bugs affecting protocol compliance.

What causes AMQP disposition settlement and flow credit issues when using the Service Bus emulator?

AMQP disposition settlement and flow credit issues are caused by protocol violations and inconsistencies between the emulator and the Azure SDK. Analyzing AMQP frames from emulator logs identifies these specific message broker property mismatches and flow control failures.