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
Context: Kafka integration with MSK using mechanism AWS_MSK_IAM, connecting admin client, consumers and producers.
Connecting Kafka clients to MSK using the "EnhancedProfileCredentialsProvider"/, whether by specifying a profile name or using the (override) default chain provider is generating a lot of warn logs similar to: WARN s.a.a.utils.cache.CachedSupplier -- (ProfileFileSupplier()) Retrieved value expiration is in the past (2025-01-27T18:16:25.592341Z). Using expiration of 2025-01-27T18:16:26.592584Z
I did not observe this behavior when using fixedProfileFile (tested on S3 integration with IAM using both suppliers), so I'd consider this an issue with the reloadWhenModified ProfileFileSupplier used by the IAMClientCallbackHandler.
I had a look at your implementation but did not figure out what is causing this logging, my understanding is that the file shouldn't be considered stale unless it has been modified since the last read, so this expiration log is confusing and not actionable.
Reproducing: My expectation is that any client connected to MSK using the credential profile provider will see this warning, despite everything working as expected?
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Context: Kafka integration with MSK using mechanism AWS_MSK_IAM, connecting admin client, consumers and producers.
Connecting Kafka clients to MSK using the "EnhancedProfileCredentialsProvider"/, whether by specifying a profile name or using the (override) default chain provider is generating a lot of warn logs similar to:
WARN s.a.a.utils.cache.CachedSupplier -- (ProfileFileSupplier()) Retrieved value expiration is in the past (2025-01-27T18:16:25.592341Z). Using expiration of 2025-01-27T18:16:26.592584Z
I did not observe this behavior when using
fixedProfileFile
(tested on S3 integration with IAM using both suppliers), so I'd consider this an issue with thereloadWhenModified
ProfileFileSupplier used by theIAMClientCallbackHandler
.I had a look at your implementation but did not figure out what is causing this logging, my understanding is that the file shouldn't be considered stale unless it has been modified since the last read, so this expiration log is confusing and not actionable.
Reproducing: My expectation is that any client connected to MSK using the credential profile provider will see this warning, despite everything working as expected?
This could be an issue for aws-sdk-java-v2, similar to Credentials reloading is not working but I've decided to create it here first as it is easier to put into context.
Edit: looks like this is known and should eventually be addresses, see aws/aws-sdk-java-v2#5839
The text was updated successfully, but these errors were encountered: