Closed jurmous closed 1 year ago
We recently started throwing this exception when a user tries to call getCredentials()
after the credentials provider is already closed. In your workflow, are you making requests using the DynamoDB client after .close()
has already been called on it?
@lauzadis I discovered I made an assumption about the KTOR lifecycle which was wrong and it worked with the AWS clients before 0.20.0-beta. Now I changed to work better with the lifecycle and to close the clients after the ktor server ends, it all works well with the new versions.
Thanks for the response, it triggered me to go deeper with a debug run.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
When I update to 0.20.0-beta or 0.20.1-beta I get a Credential Provider closed exception as soon as I try to communicate with a local DynamoDB instance.
Probably it is related to #824?
Expected behavior
No crashes on closed Credential Providers
Current behavior
Crash:
Steps to Reproduce
Possible Solution
Downgrade for now to 0.19.4-beta
Context
No response
AWS Kotlin SDK version used
0.20.1-beta
Platform (JVM/JS/Native)
JVM
Operating System and version
MacOS 13.1