Releases: apache/pulsar-dotpulsar
Releases · apache/pulsar-dotpulsar
DotPulsar 3.3.0
Added
Producer properties can be added when creating a producer
Changed
Updated the Microsoft.Extensions.ObjectPool dependency from version 8.0.4 to 8.0.6
DotPulsar 3.3.0-rc.1
Added
Producer properties can be added when creating a producer
Changed
Updated the Microsoft.Extensions.ObjectPool dependency from version 8.0.4 to 8.0.6
DotPulsar 3.2.1
Fixed
RoundRobinPartitionRouter and SinglePartitionRouter could return a negative number. They have been changed to ensure they always return a non-negative integer.
DotPulsar 3.2.1-rc.1
Fixed
RoundRobinPartitionRouter and SinglePartitionRouter could return a negative number. They have been changed to ensure they always return a non-negative integer.
DotPulsar 3.2.0
Added
IReceive now has a 'TryReceive' extension method allowing for non-blocking retrieval of buffered messages
Changed
Updated the Microsoft.Extensions.ObjectPool dependency from version 8.0.1 to 8.0.3
Fixed
Disposing a newly created consumer or reader could result in an exception being thrown
Concurrent 'Receive' invocations on a partitioned topic could result in an exception being thrown
DotPulsar 3.2.0-rc.1
Added
IReceive now has a 'TryReceive' extension method allowing for non-blocking retrieval of buffered messages
Changed
Updated the Microsoft.Extensions.ObjectPool dependency from version 8.0.1 to 8.0.3
Fixed
Disposing a newly created consumer or reader could result in an exception being thrown
Concurrent 'Receive' invocations on a partitioned topic could result in an exception being thrown
3.1.2
Fixed
- When sending a message that is too large the broker will close the tcp connection, causing the producer to disconnect, reconnect, and retry in an endless loop.
Now a TooLargeMessageException is thrown (will be given to the exception handler) and the producer's state is changed to 'Faulted' - A race condition could cause Send(..) operations of the producer to hang after a reconnect
3.1.2-rc.1
Fixed
- When sending a message that is too large the broker will close the tcp connection, causing the producer to disconnect, reconnect, and retry in an endless loop.
Now a TooLargeMessageException is thrown (will be given to the exception handler) and the producer's state is changed to 'Faulted' - A race condition could cause Send(..) operations of the producer to hang after a reconnect
3.1.1
Fixed
- Fixed a bug where disposing a disconnected consumer, reader or producer would cause a hang
Full Changelog: 3.1.0...3.1.1
3.1.1-rc.1
Fixed
- Fixed a bug where disposing a disconnected consumer, reader or producer would cause a hang