Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How does the parameter “Time Period for Duplicate Check for EO(IO) (secs)” work?

April 26, 2017duplicate EO IO parameter period time

0

Posted

How does the parameter “Time Period for Duplicate Check for EO(IO) (secs)” work?

1 Answer

0

Posted

This parameter is used as a “house-keeping” parameter to store jms message ids for duplicate checking in the XI_AF_SVC_ID_MAP table which has the following schema: MSG_ID1 (varchar), MSG_ID2 (varchar), PERSIST_UNTIL (timestamp). This parameter specifies the “MINIMUM” time period for which the mapping is held in the table after which it would be removed to prevent database/table overflow . However it can not be guaranteed that the mapping is removed at the exact time, since it is dependent on a background job which runs at regular intervals and removes all the expired maps. This background job cannot be modified to run at an exact time or any conditions such as PERSIST time, expiry time etc be introduced here, since such properties are handled on the server side. The duplicate check time period has nothing to do with the JMSExpiration property which is actually handled on the server side. JMS Adapter is a JMS client and does not support the JMSExpiration period as such.