Hi Team,

We are using JDBC  Idempotent repository in our project . recently we ran into 
a issue where the exchange failed in first run and after couple of  retry  it 
was success .
But the idempotent consumer removed message ID from JDBC table , since exchange 
failed first time.

.idempotentConsumer(simple("${header.kafka.TOPIC}_${header.kafka.PARTITION}_${header.kafka.OFFSET}"))
                                        
.messageIdRepositoryRef("IdempotentRepo")
                                        .eager(true)
                                        .completionEager(false)
                                        .skipDuplicate(false)

Is there a way to manually insert message ID into repository in code at the end 
of my route. rather than being driven by properties eager and CompletionEager.

Thanks,
shiva
________________________________
NOTICE: All information in and attached to the e-mails below may be 
proprietary, confidential, privileged and otherwise protected from improper or 
erroneous disclosure. If you are not the sender's intended recipient, you are 
not authorized to intercept, read, print, retain, copy, forward, or disseminate 
this message. If you have erroneously received this communication, please 
notify the sender immediately by phone (704-758-1000) or by e-mail and destroy 
all copies of this message electronic, paper, or otherwise. By transmitting 
documents via this email: Users, Customers, Suppliers and Vendors collectively 
acknowledge and agree the transmittal of information via email is voluntary, is 
offered as a convenience, and is not a secured method of communication; Not to 
transmit any payment information E.G. credit card, debit card, checking 
account, wire transfer information, passwords, or sensitive and personal 
information E.G. Driver's license, DOB, social security, or any other 
information the user wishes to remain confidential; To transmit only 
non-confidential information such as plans, pictures and drawings and to assume 
all risk and liability for and indemnify Lowe's from any claims, losses or 
damages that may arise from the transmittal of documents or including 
non-confidential information in the body of an email transmittal. Thank you.

Reply via email to