Interlok 4071 expose timeout options #1167
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
So we can expose the timeout options that are available in the standard http producer.
Modification
Updated the class HttpRequestServiceImp so it gives the timeout options in the UI and when creating a StandardHttpProducer object we pass in the timeout values that have been set.
Also added a new unit test that tests that the read timeout will throw an exception if it is exceeded.
PR Checklist
Result
The end user is now able to choose and swet connect and read timeout durations when using this service.
Testing
You can create a channel->workflow that creates a request using a polling consumer and the HttpRequestService(making sure you have the read timeout set) then create a second channel->workflow that can mock a http endpoint by using a Jetty connection and consumers. Within that workflow include a wait service followed by a jetty response service. Make sure the wait service time period is longer than whatever the read timeout is.