Repository navigation
v5.7.0
What's New
- Configure the Avro, JSON and Protobuf schema registry serializers and deserializers through dedicated builders (e.g.
KafkaJsonSerializerConfigurationBuilder), consistently with the other Kafka settings; theConfigureoverloads taking the Confluent configuration are now obsolete - Add
EnableSaslOauthbearerAssertionClaimJtiandDisableSaslOauthbearerAssertionClaimJtito the Kafka client configuration builders, consistently with the other boolean settings - Execute custom code when an error policy is about to be applied
Fixes
- Mark the parent of the consume activity as remote when the trace context is restored from the message headers [#267]
- Start the produce activity when the outbox worker produces the stored messages, continuing the trace stored in the message headers
- Set the message id, partition and Kafka key tags on the produce activity
- Rethrow the original exception instead of wrapping it into a
TargetInvocationExceptionwhen a synchronous subscriber throws [#177] - Prevent the asynchronous broker client callbacks from failing when a scoped callback or one of its dependencies only implements
IAsyncDisposable - Prevent a deadlock when a sequence (e.g. a batch) is aborted while it is being completed or disposed
- Prevent adding to, completing or aborting a sequence (e.g. a batch) from hanging when it is disposed concurrently
- Commit the last processed message and keep consuming when a batch subscriber stops enumerating before the end of the batch
- Prevent a batch from hanging when its timeout elapses while the subscriber stops enumerating
- Prevent the consumer from looping endlessly when a chunked message in a batch isn't fully read
- Prevent the consumer stop from failing or completing too early when a new sequence (e.g. a batch) starts while stopping
- Prevent the consumer from processing one more buffered message while stopping or disconnecting
- Roll back instead of applying the error policies when the consumer stop cancels the processing
- Prevent the consumer
StopAsyncfrom hanging when the processing it waits for stops or reconnects the consumer (e.g. through the error policies) - Prevent a reconnect (e.g. the Kafka auto recovery) from restarting a consumer that is stopped or being stopped
- Prevent the broker clients from connecting or disconnecting twice when concurrent calls overlap (e.g. the shutdown racing a reconnect)
- Prevent Kafka consumers from skipping the messages already fetched but not yet processed when stopped and restarted
- Prevent a Kafka partition from staying paused when the consumer is stopped and restarted, or the partition is revoked and assigned again, while rolling it back
- Keep consuming when a Kafka consumer is restarted right after a non-blocking stop
- Prevent a Kafka partition assignment or rollback racing the consumer stop from treating the stopped consumer as still started
- Prevent a possible native crash when offsets are stored or committed while the Kafka consumer is being disconnected
- Prevent MQTT consumers from leaving the message being read or retried unprocessed when stopped and restarted
- Prevent MQTT consumers from resuming consuming when stopped again before a pending restart is completed
- Report the MQTT consumer as connected again (instead of stopped) when it is restarted while the client is still connected
- Prevent a misleading MQTT connection error warning from being logged when the client is disconnected during a connection attempt
- Allow tombstone messages (null body) to be stored in the Sqlite, PostgreSQL and Entity Framework outbox
- Prevent the in-memory Kafka topic
GetAllMessagesand the in-memory MQTT brokerGetMessagesfrom failing when messages are produced concurrently - Prevent an exception in a partitions revoked callback from interrupting the rebalance of the other consumers in the mocked Kafka
Important
The [Required] attribute has been removed from SilverbackOutboxMessage.Content. When using the Entity Framework outbox, add a migration to drop the NOT NULL constraint from the Content column, otherwise storing a tombstone will still fail.
See docs for details.