Amraneze opened a new pull request, #24973:
URL: https://github.com/apache/beam/pull/24973

   Add a retry policy to publish messages in case of connection closed
   
   Fixes#24971
   
   Co-Authored-By: Amrane Ait Zeouay 
<[email protected]>
   
   When trying to publish messages using `JmsIO` with a closed/failed 
connection, the messages are not published and lost. We will need to get the 
failed messages with the function `getFailedMessages` and try again and again 
multiple times. 
   
   ````java
   var failedPublishedMessages = 
messages.apply(getWriter(sinkOptions)).getFailedMessages();
   var refailedPublishedMessages = 
failedPublishedMessages.apply(REPUBLISH_FAILED_MESSAGE_NAME, 
getWriter(sinkOptions)).getFailedMessages();
   ....
   return PDone.in(cdpMessages.getPipeline());
   ````
   
   To not have multiple steps for retrying the failed publication, we added a 
`Retry Policy` which consist on retrying the publication n times (the number is 
given by the user) until the timeout (given by the user too) is finished. Also, 
we added a predicate function, to give the user the option to handle when the 
connection should be reconnected or not in case of a failed connection.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable. This will automatically add a link to the 
pull request in the issue. If you would like the issue to automatically close 
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
    - [ ] Update `CHANGES.md` with noteworthy changes.
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   See the [Contributor Guide](https://beam.apache.org/contribute) for more 
tips on [how to make review process 
smoother](https://beam.apache.org/contribute/get-started-contributing/#make-the-reviewers-job-easier).
   
   To check the build health, please visit 
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
   
   GitHub Actions Tests Status (on master branch)
   
------------------------------------------------------------------------------------------------
   [![Build python source distribution and 
wheels](https://github.com/apache/beam/workflows/Build%20python%20source%20distribution%20and%20wheels/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
   [![Python 
tests](https://github.com/apache/beam/workflows/Python%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Java 
tests](https://github.com/apache/beam/workflows/Java%20Tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
   [![Go 
tests](https://github.com/apache/beam/workflows/Go%20tests/badge.svg?branch=master&event=schedule)](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
   
   See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more 
information about GitHub Actions CI.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to