Spring/spring-amqp
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

GH-1347: DMLC Ignored Authentication Failures

Browse Source 
Resolves https://github.com/spring-projects/spring-amqp/issues/1347

Container starts and keeps trying to connect instead of honoring
the property.

**cherry-pick to 2.2.x**
This commit is contained in:
Gary Russell
2021-06-08 17:19:04 -04:00
committed by Artem Bilan
parent 8e8dda721f
commit ea97b1179c
4 changed files with 43 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/reference/asciidoc/amqp.adoc
View File

@@ -6146,11 +6146,17 @@ FailureFatal
(possible-authentication-
failure-fatal)
a|When set to `true` (default), if a `PossibleAuthenticationFailureException` is thrown during connection, it is considered fatal.
This causes the application context to fail to initialize during startup.
a|When set to `true` (default for SMLC), if a `PossibleAuthenticationFailureException` is thrown during connection, it is considered fatal.
This causes the application context to fail to initialize during startup (if the container is configured with auto startup).
Since _version 2.0_.
**DirectMessageListenerContainer**
When set to `false` (default), each consumer will attempt to reconnect according to the `monitorInterval`.
**SimpleMessageListenerContainer**
When set to `false`, after making the 3 retries, the container will go into recovery mode, as with other problems, such as the broker being down.
The container will attempt to recover according to the `recoveryInterval` property.
During each recovery attempt, each consumer will again try 4 times to start.