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
We are using LexRuntimeV2AsyncClient to create a connection with Lex.
After the conversation, we want to close the client so any resource left is discarded using LexRuntimeV2AsyncClient.close()
But while closing the client, we are having a warning with a TimeoutException in the closing event loop:
We tried to override the connectionAcquisitionTimeout using an httpClientBuilder as described on this issue. That was tested locally, the error continues to appear, and while debugging we can see that those 10 seconds are actually hardcoded.
We also noticed that timeout in software.amazon.awssdk.http.nio.netty.internal.AwaitCloseChannelPoolMap is also hardcoded:
Is there a way to configure these timeout configurations with client LexRuntimeV2AsyncClient?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are using LexRuntimeV2AsyncClient to create a connection with Lex.
After the conversation, we want to close the client so any resource left is discarded using
LexRuntimeV2AsyncClient.close()
But while closing the client, we are having a warning with a TimeoutException in the closing event loop:
We tried to override the connectionAcquisitionTimeout using an httpClientBuilder as described on this issue. That was tested locally, the error continues to appear, and while debugging we can see that those 10 seconds are actually hardcoded.
We also noticed that timeout in
software.amazon.awssdk.http.nio.netty.internal.AwaitCloseChannelPoolMap
is also hardcoded:Is there a way to configure these timeout configurations with client LexRuntimeV2AsyncClient?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions