Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improvement]: Defining timeout values in milliseconds instead of seconds in AWS SQS Connector #3690

Open
VinulaUthsara opened this issue Oct 21, 2024 · 0 comments

Comments

@VinulaUthsara
Copy link

Description

It is not possible to define timeout values in milliseconds for the SQS connector initialization configuration. Our documentation [1] states that these values should be defined in seconds, while the AWS documentation [2] specifies milliseconds.

[1] https://mi.docs.wso2.com/en/latest/reference/connectors/amazonsqs-connector/2.x/amazonsqs-connector-2.x-reference/
[2] https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/core/RequestOverrideConfiguration.html#apiCallAttemptTimeout()

Describe your problem(s)

No response

Describe your solution(s)

Ideally the SQS Connector configurations should allow defining these values in milliseconds.

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

AmilaSamith added a commit to AmilaSamith/esb-connector-amazonsqs that referenced this issue Oct 22, 2024
This change allows time configuration values to be provided in milliseconds, with support for specifying the time in decimal seconds Fixes:wso2/product-micro-integrator#3690
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant