[BUG] servicebus
binder response with status=DOWN
if it can't process the event due to message payload size
#44158
Labels
azure-spring
All azure-spring related issues
azure-spring-servicebus
Spring service bus related issues.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-triage
Workflow: This issue needs the team to triage.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Describe the bug
servicebus
binder response withstatus=DOWN
for the liveness probe if it can't process the event due to message payload size. Because of theservicebus
binder status asDOWN
, the status of the liveness probe isDOWN
as well (despite the application itself being up and running). liveness probe is used in the K8S cluster for the application health cheks. Its incorrect status makes the pod to recreate the container, although the application itself is healthy.Exception or Stack Trace
The binder throws the exception with the message
Size of the payload exceeded maximum message size: 256 kb
.The stack trace is also available in the liveness probe response (please find it below in the
actuator livenerr probe response
section).To Reproduce
Service Bus standard tier has a limitation for the payload of 256kb. If the single event has a payload that exceeds this limit, the binder throws
ServiceBusException
and binder status is considered down.Expected behavior
servicebinder
probe should reportUP
in the case the message payload can't be processed due to its size.Setup
spring-cloud-azure-stream-binder-servicebus
's5.6.0
and5.14.0
Actuator liveness probe response
The text was updated successfully, but these errors were encountered: