You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I send a large number of messages to Event Hub, there is a issue that the Consumer side cannot retrieve the messages.
azure-messaging-eventhubs : 5.10.0
From the following log, it appears that EventHubsProcessorClient is not retrieving data.
OverflowException: The receiver is overrun by more signals than expected (bounded queue...)
at prototype.TestConsumer.lambda$1(TestConsumer.java:83)
at com.azure.messaging.eventhubs.EventProcessorClientBuilder$1.processError(EventProcessorClientBuilder.java:619)
at com.azure.messaging.eventhubs.PartitionPumpManager.handleError(PartitionPumpManager.java:338)
at com.azure.messaging.eventhubs.PartitionPumpManager.lambda$startPartitionPump$3(PartitionPumpManager.java:239)
at reactor.core.publisher.LambdaSubscriber.onError(LambdaSubscriber.java:149)
at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.doError(FluxPublishOn.java:511)
at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.checkTerminated(FluxPublishOn.java:569)
at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:432)
at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:527)
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84)
at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: reactor.core.Exceptions$OverflowException: The receiver is overrun by more signals than expected (bounded queue...)
at reactor.core.Exceptions.failWithOverflow(Exceptions.java:220)
at reactor.core.publisher.FluxWindowTimeout$WindowTimeoutSubscriber.drainLoop(FluxWindowTimeout.java:363)
at reactor.core.publisher.FluxWindowTimeout$WindowTimeoutSubscriber$ConsumerIndexHolder.run(FluxWindowTimeout.java:448)
at reactor.core.scheduler.PeriodicWorkerTask.call(PeriodicWorkerTask.java:59)
at reactor.core.scheduler.PeriodicWorkerTask.run(PeriodicWorkerTask.java:73)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
As a workaround, lowering the version to [azure-messaging-eventhubs 5.9.0] no longer reproduces the issue.
Based on the above, I believe that the issue of stopping receiving messages from partitions is occurring when using the version of "azure-messaging-eventhubs : 5.10.0".
【Question】
Could you please let me know why the version [azure-messaging-eventhubs : 5.10.0] stops receiving messages from the partition?
If the problem is specific to the [azure-messaging-eventhubs : 5.10.0] version, I hope it will be fixed.``
The text was updated successfully, but these errors were encountered:
If I send a large number of messages to Event Hub, there is a issue that the Consumer side cannot retrieve the messages.
azure-messaging-eventhubs : 5.10.0
From the following log, it appears that EventHubsProcessorClient is not retrieving data.
As a workaround, lowering the version to [azure-messaging-eventhubs 5.9.0] no longer reproduces the issue.
Based on the above, I believe that the issue of stopping receiving messages from partitions is occurring when using the version of "azure-messaging-eventhubs : 5.10.0".
・Similar issues
TITLE : Azure/azure-sdk-for-java
URL : Azure/azure-sdk-for-java#24426
TITLE : Azure/azure-sdk-for-java
URL : Azure/azure-sdk-for-java#24575
【Question】
Could you please let me know why the version [azure-messaging-eventhubs : 5.10.0] stops receiving messages from the partition?
If the problem is specific to the [azure-messaging-eventhubs : 5.10.0] version, I hope it will be fixed.``
The text was updated successfully, but these errors were encountered: