[BUG] Addition of the application properties in spring boot is not reflecting any changes

[Sowmya192319]

Describe the bug
We added the following properties in application properties of the spring boot to increase the delay between the message retries. But it's reflecting the delays between retries.

spring.cloud.azure.servicebus.consumer.retry.fixed.delay=60000
spring.cloud.azure.servicebus.consumer.retry.mode=FIXED
spring.cloud.azure.servicebus.processor.max-auto-lock-renew-duration=120000

Exception or Stack Trace
No exceptions

To Reproduce
Add the above properties in application properties, send some error message, which leads to retry code.

Code Snippet
#Service Bus connection
spring.cloud.azure.servicebus.client.transport-type=AMQP_WEB_SOCKETS
spring.cloud.azure.servicebus.consumer.client.transport-type=AMQP_WEB_SOCKETS
spring.cloud.azure.servicebus.processor.client.transport-type=AMQP_WEB_SOCKETS
spring.cloud.azure.servicebus.producer.client.transport-type=AMQP_WEB_SOCKETS
spring.cloud.azure.servicebus.consumer.retry.fixed.delay=60000
spring.cloud.azure.servicebus.consumer.retry.mode=FIXED
spring.cloud.azure.servicebus.processor.max-auto-lock-renew-duration=120000

Expected behavior
To see the delays between the retries when reading the message from azure service bus queue

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• OS: Linux and Mac IOS
• IDE: IntelliJ
• Library/Libraries: spring-cloud-azure-starter-servicebus ( 5.19.0_
• Java version: 21
• App Server/Environment: Embedded tomcat server
• Frameworks: Spring Boot

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

• verbose dependency tree (mvn dependency:tree -Dverbose)
• exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[anuchandy]

@Sowmya192319, the retry configurations are scoped only to the transient errors (e.g., connection lost, retryable link errors from broker). By design, application-level errors (e.g., error thrown by app, messages that app use to represent business errors) are outside the scope of the library's retry mechanism.

[joshfree]

the retry configurations are scoped only to the transient errors (e.g., connection lost, retryable link errors from broker). By design, application-level errors (e.g., error thrown by app, messages that app use to represent business errors) are outside the scope of the library's retry mechanism.

Adding issue-addressed label for @anuchandy's post above

[github-actions]

Hi @Sowmya192319. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.