BackOff | A back-off strategy interface for retrying operations | Functional Testing library

After seeing whole log line entry

You don't need all the standard @KafkaListener method invoking infrastructure when your listener already implements one of the message listener interfaces; instead of registering endpoints for each listener, just create a container for each from the factory and add the listener to the container properties.

Your issue is here enable.auto.commit = false. If you are not manually committing offset after consuming messages, You should configure this to true

If this is set to false, after consuming messages from Kafka, there is no feedback to Kafka whether you read or not. Then after you restart your consumer it will send messages from the start. If you enable this, your consumer make sure it will automatically send your last read offset to Kafka. Then Kafka saved that offset in __consumer_offsets topic with your consumer group_id, topic you consumed and partition.

Then after you restart the consumer, Kafka read your last position from __consumer_offsets topic and send from there.

Pretty simple. Values of uint8_t are 0 to 255. You need at least uint32_t (uint16_t max 65535). 224 is the bits of the real answer that fit in the 8 bit int.

1. BOOL setsomethingfunc(UINT8 value) your function should take pointer not the integer. It has to be BOOL setsomethingfunc(UINT8 *value)

2. Use standard C types. uint8_t for 8 bits unsigned integer and bool from stdbool.h. Many old code (or the code which development started long time ago like Linix kernel) use those non standard types for historical reasons. You should learn the modern C

I think something like this may work for you:

I am not a Spring user, but interested in all things AOP, both AspectJ and Spring AOP. I liked your little puzzle. Thanks to your MCVE, I was able to reproduce the issue and debug into it. This is a perfect example for why an MCVE is so much superior to simply posting a bunch of code snippets. So thanks for that, please keep up this way of asking questions.

When looking at the situation in a debugger, you see that while the aspect is proceeding into triggerJob, at some point we are in method AnnotationAwareRetryOperationsInterceptor.invoke and there we have the following code:

The retry options apply to a single service operation performed by the Service Bus SDK and are intended to allow the SDK work around short-term transient issues, like the occasional network interruption. Other than configuring the SDK clients, the Functions infrastructure is unaware of the retries and would simply see the SDK taking a longer time to perform the requested read/publish operation.

The Functions infrastructure will apply any execution time limits imposed by the runtime or may decide to take action to guard against an unresponsive service operation. (disclaimer: I can speak to the Service Bus SDK, but don't have deep insight into the Functions runtime)

The retries from the Service Bus extensions aren't applied to your Function code; on an error in your code you'll end up in an exception scenario and, depending on configuration and trigger/binding use, will either see your message abandoned or the lock held until timeout.

I'm not sure of your exact scenario, but it seems like you may want to consider deferring the message to be read explicitly at a later time or re-enqueuing the message with a schedule so that the Function can read again at a specific point in the future.

There is no problem with the code and it works fine on my side. And the error message shows the reason:

azure.core.exceptions.ResourceNotFoundError: (SubscriptionNotFound) The subscription 'xxxx' could not be found. Code: SubscriptionNotFound Message: The subscription 'xxxx' could not be found.

It seems you run the python code in your local machine. I recommend you log in with the Azure CLI first and then check if the subscription id that you used in your python code is right.