on 07-18-2022 3:57 PM
Hi Community,
I understand using JMS adapter we can store message in queue , and if target system is not reachable then it will keep trying to reprocess message until target system is reachable.
Can't this be stopped after particular number of retries and later processed by manually from queue ?
If it tries continuously to reprocess , will it not affect on system performance ?
Thanks,
Nikhil
Hi nikhil.85,
No, in JMS reprocessing can't be stopped after particular number of retries.It will retry indefinitely as per the configuration and only way to stop is to remove the message from the JMS queue after certain number of retries as mentioned in the other answer.If you do no like to remove it from the queue, then keep the big number in maxium retry interval and tick the exponential backoff so that retry happend after long delays and in the meantime if the target system is up, manually retrigger it from the queue.Regards,SunnyYou must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi nikhil.85
"If it tries continuously, it may impact the system depending on the integration interface design"As I have already mentioned, take care of the following configurations of JMS Sender Adapter for controlling the retries and preventing the frequent retries in a short span of time:
1. Retry interval,
2. Maxium retry interval
3, Exponential backoff
Keep the big number in maxium retry interval and tick the exponential backoff so that retry happend after long delays and in the meantime if the target system is up, manually retrigger it from the queue.
Regards,Sunny
Hi Nikhil,
you can keep count of JMS retries using header SAPJMSRetries and stop retry once the count is reached.
You can refer to the below blog post.
Regards,
Priyanka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Priyanka,
Thanks for response , I have already used SAPJMSRetries , in exception sub process referring this This blog . It retries 5 times as per configuration and don't trigger next steps in exception sub process after RetryConfigruation process call (as expected ) and after 5 retires it triggers alert as per configuration which is fine , but it tries keep retrying until connection is not reachable or message is not completed successful.any sugeestions ?
User | Count |
---|---|
75 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.