AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-diagnostics

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-diagnostics at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 42

troubleshooting/messaging/azure-servicebus-java.md

Azure Service Bus SDK — Java

Package: azure-messaging-servicebus | README | Full Troubleshooting Guide

Common Errors

| Exception | Cause | Fix | |-----------|-------|-----| | AmqpException (unauthorized-access) | Bad credentials or missing permissions | Verify connection string, SAS, or RBAC roles | | AmqpException (connection:forced) | Idle connection or transient network issue | Auto-recovers; no action needed | | ServiceBusException (MESSAGE_LOCK_LOST) | Lock expired during processing | Reduce processing time, disable auto-complete, settle manually |

Key Issues

Processor hangs with high prefetch + maxConcurrentCalls

Update disposition request timed out. — Client stops processing new messages.

Cause: Thread starvation when thread pool size ≤ maxConcurrentCalls.

Fix:

# Increase reactor thread pool
-Dreactor.schedulers.defaultBoundedElasticSize=<value greater than concurrency>

Also set prefetchCount(0) to disable prefetch. This is more frequent in AKS environments.

Implicit prefetch in ServiceBusReceiverClient

Even with prefetch disabled in the builder, receiveMessages API can re-enable prefetch implicitly. See SyncReceiveAndPrefetch.

Autocomplete issues

Autocomplete and auto-lock-renewal have known issues with buffered/prefetched messages.

Fix: Use disableAutoComplete() and .maxAutoLockRenewalDuration(Duration.ZERO), then settle messages explicitly.

Enable Logging

Configure via SLF4J:

<logger name="com.azure.messaging.servicebus" level="DEBUG"/>

See Java SDK logging docs for details.

Filing Issues

Include: namespace tier, entity type/config, machine specs, max heap (-Xmx), maxConcurrentCalls, prefetchCount, autoComplete setting, traffic pattern, and DEBUG-level logs (±10 min from issue).