7.18.0-beta.2 (2026-06-22)
Features Added
- Added
drainTimeout(Duration)toServiceBusProcessorClientBuilderandServiceBusSessionProcessorClientBuilderto configure the maximum wait time for in-flight message handlers during processor shutdown. Defaults to 30 seconds.
Bugs Fixed
- Fixed
ServiceBusProcessorClient.close()disposing the receiver before in-flight message handlers could complete settlement, causingIllegalStateException. The processor now drains active handlers before closing. (#45716) - Fixed
ServiceBusMessageBatchaccepting messages beyond the service-enforced batch size limit on
Premium large-message entities by reading thecom.microsoft:max-message-batch-sizevendor property
from the AMQP sender link instead of usingmax-message-size. (#48214) - Fixed
ServiceBusAdministrationClient.updateSubscription()silently ignoringdefaultMessageTimeToLivechanges. The property was incorrectly nullified before serialization. (#48495)
Other Changes
- Implemented support for the
com.microsoft:max-message-batch-sizeAMQP vendor property in
createMessageBatch. The Service Bus service has advertised this property on sender links for some
time to communicate the broker-enforced batch size limit; the SDK now reads it and sizes batches
against this value, falling back tomax-message-sizewhen the property is absent. Previously the
batch path usedmax-message-sizedirectly, which on Premium large-message entities (link advertises
up to 100 MB while the batch limit stays at 1 MB) caused the broker to reject oversized batches.
Single-message sends (sendMessage,scheduleMessage) continue usingmax-message-size.
(#48214)