Submit Search

Retry Request to the Backend Route

This route implements the retry mechanism. The route checks the number of retry attempts and decides if another attempt is needed. The key components that make up the retry mechanism are Data Storage and Groovy components.

Route Structure

Route Components Description

Component Name	Component Type	Description
Timer Reporting	Timer Reporting	Continuously generates a trigger message at intervals of 1 second to activate the Get Data component.
Get Data	Data Storage Inbound	Picks up data from the /requests location in XEServer Data Storage.
Check Retry Attempts	Groovy	Executes the groovy script that applies the following logic: If 10 or more seconds have passed since the last retry attempt and the current number of attempts is less than 3 - the "Flow" message exchange property is set with a value of "retry". Otherwise, the "Flow" message exchange property is set as "timeout". In-memory Groovy script: MAX_ATTEMPTS = 3 ATTEMPT_TIMEOUT = 10 //seconds attempt = Attempt as Integer timeSinceLastAttempt = (System.currentTimeMillis() - Date.parse("yyyyMMdd-HHmmss", LastAttempt).time) / 1000 flow = "" if(timeSinceLastAttempt >= ATTEMPT_TIMEOUT) { if(attempt < (MAX_ATTEMPTS - 1)) { context.exchange.properties["Attempt"] = attempt + 1 flow = "retry" } else { flow = "timeout" } } context.exchange.properties["Flow"] = flow The original data is directed further down the route through the original output.
Is Retry?	Router	Checks the XEServer message exchange "Flow" property, and depending on its value, directs the data to either the retry or the timeout output.
Request To Backend	Subroute	Sends data to the Request to Backend route to be processed one more time.
Back to system	JMS Outbound	Sends the data to the back-end system (REST Request Processing route).