Page Sequence Monitor (PSM) doesn't appear to do retries
Description
A customer reported that retries don't seem to be working and verified myself in one of the unit tests by setting a "retry" parameter on any of the tests. Looks the retries were attempted to be implemented with the DefaultHttpMethodRetryHandler and perhaps that doesn't work as expected.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Donald Desloge April 14, 2011 at 3:15 PM
You can now retry entire sequences with the following parameter.
This is trickier than it looks, pushing until 1.8.11 and 1.9.8 for now.
Donald Desloge April 4, 2011 at 5:11 PM
Reverted back to retry. UnitTests all had retries but the PollerConfig uses retry instead.
Donald Desloge April 4, 2011 at 4:58 PM
The retry only occurs when an IOException happens, this is the default behavior of the HttpClient. If it can't make a successful http method call it will retry.
Donald Desloge April 4, 2011 at 4:23 PM
The PageSequenceMonitor was checking for the wrong parameter for retries. Renamed retry to retries, this should be fixed now.
A customer reported that retries don't seem to be working and verified myself in one of the unit tests by setting a "retry" parameter on any of the tests. Looks the retries were attempted to be implemented with the DefaultHttpMethodRetryHandler and perhaps that doesn't work as expected.