Closed jorgenota closed 3 years ago
@jorgenota Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
@jorgenota Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
@jorgenota Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
@jorgenota Thank you for signing the Contributor License Agreement!
0
in this case means short polling - not indefinite timeout. With milliseconds - agreed this should be changed, but we need to think if we do it for 2.4 or 3.0.
Can you move this PR to https://github.com/awspring/spring-cloud-aws? This repository is only used for the 2.2.x maintenance.
0
in this case means short polling - not indefinite timeout.
Yes, '0' means short polling. According to javadoc of PollableChannel, receive() method "Receive a message from this channel, blocking indefinitely if necessary". That's why I suggested using MessageChannel.INDEFINITE_TIMEOUT constant in line 204 (instead of 0).
Am I right? Should I move my PR as it is right now (or change only the transformation to seconds)?
Can you move this PR to https://github.com/awspring/spring-cloud-aws? This repository is only used for the 2.2.x maintenance.
Of course, thanks for the clarification.
Replaced with https://github.com/awspring/spring-cloud-aws/pull/123
:loudspeaker: Type of change
:scroll: Description
Minor changes to better handle timeout parameter when receiving messages from an SQS queue.
:bulb: Motivation and Context
I suggest this fixes to align with PollableChannel interface:
:pencil: Checklist
:crystal_ball: Next steps