Troubleshooting messaging transports New in 1.14.0
Diagnose Wolverine messaging transport failures across RabbitMQ, Azure Service Bus, AWS SQS/SNS, Kafka, NATS, Pulsar, MQTT, Redis and SignalR: InvalidListenerConfigurationException, 'does not support EndpointMode.NativeAck', MissingNamedConnectionStringsException, the 'has not been initialized' family, 'does not (yet) support conventional routing to multiple handlers', MessageTooLargeException and SqsMessageTooLargeException, init wrappers whose InnerException is the answer, the 'broker entity does not exist' loop, and log-only silent stops. One reference page per broker holds every verbatim message with its trigger and fix.
Use when a host fails at startup on a transport, a listener goes quiet, a send is discarded, or a broker error needs decoding.
Skill details
- Skill name:
wolverine-troubleshooting-transports - Applies to:
wolverine - Tags:
troubleshooting,transports,messaging,rabbitmq,azure-service-bus,sqs,sns,kafka,nats,pulsar,mqtt,redis,signalr,InvalidListenerConfigurationException,MissingNamedConnectionStringsException,MessageTooLargeException,NativeAck,conventional-routing,aspire - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.