Unable to configure Azure Event Hub Producer

Question

I am trying a sample code of Azure Event Hub Producer and trying to send some message to Azure Event Hub.

The eventhub and its policy is correctly configured for sending and listening messages. I am using Dotnet core 3.1 console application. However, the code doesn't move beyond CreateBatchAsync() call. I tried debugging and the breakpoint doesn't go to next line. Tried Try-catch-finally and still no progress. Please guide what I am doing wrong here. The Event hub on Azure is shows some number of successful incoming requests.

    class Program
    {
        private const string connectionString = "<event_hub_connection_string>";
        private const string eventHubName = "<event_hub_name>";
        static async Task Main()
        {
            // Create a producer client that you can use to send events to an event hub
            await using (var producerClient = new EventHubProducerClient(connectionString, eventHubName))
            {
                // Create a batch of events 
                using EventDataBatch eventBatch = await producerClient.CreateBatchAsync();

                // Add events to the batch. An event is a represented by a collection of bytes and metadata. 
                eventBatch.TryAdd(new EventData(Encoding.UTF8.GetBytes("First event")));
                eventBatch.TryAdd(new EventData(Encoding.UTF8.GetBytes("Second event")));
                eventBatch.TryAdd(new EventData(Encoding.UTF8.GetBytes("Third event")));

                // Use the producer client to send the batch of events to the event hub
                await producerClient.SendAsync(eventBatch);
                Console.WriteLine("A batch of 3 events has been published.");
            }
        }
}

Answer 1

The call to CreateBatchAsync would be the first need to create a connection to Event Hubs. This indicates that you're likely experiencing a connectivity or authorization issue.

In the default configuration you're using, the default network timeout is 60 seconds and up to 3 retries are possible, with some back-off between them.

Because of this, a failure to connect or authorize may take up to roughly 5 minutes before it manifests. That said, the majority of connection errors are not eligible for retries, so the failure would normally surface after roughly 1 minute.

To aid in your debugging, I'd suggest tweaking the default retry policy to speed things up and surface an exception more quickly so that you have the information needed to troubleshoot and make adjustments. The options to do so are discussed in this sample and would look something like:

var connectionString = "<< CONNECTION STRING FOR THE EVENT HUBS NAMESPACE >>";
var eventHubName = "<< NAME OF THE EVENT HUB >>";

var options = new EventHubProducerClientOptions
{
    RetryOptions = new EventHubsRetryOptions
    {
        // Allow the network operation only 15 seconds to complete.
        TryTimeout = TimeSpan.FromSeconds(15),

        // Turn off retries        
        MaximumRetries = 0,
        Mode = EventHubsRetryMode.Fixed,
        Delay = TimeSpan.FromMilliseconds(10),
        MaximumDelay = TimeSpan.FromSeconds(1)
    }
};

await using var producer = new EventHubProducerClient(
    connectionString,
    eventHubName,
    options);