File sender adapter generates duplicate message IDs.

July 10, 2009 at 5:37 am

[] [] [] [] [] [] [] [] [] [] []

  1. FTP receiver adapter deletes file with append modeSymptom You are using the File Adapter in your business scenario for message processing. During the message processing, you notice, that, the FTP receiver adapter deletes the output file if it encounters...
  2. File adapter metadata changed for adapter attributesSymptom You are using the File Adapter in your business scenario for message processing. During the transport of XI to another system, you notice that the values for some of the File...
  3. File adapter: NegativeArrayException occurs while ArchivingSymptom You have configured the File Adapter in your scenario with following options set in configuration: 1.Files are to be archived (with or without timestamp) after processing. 2.Local file system (and not...
  4. Receiver file adapter thread hangingSymptom The thread of receiver file adapter remains in runnable state while communication channel has the following configuration File Construction Mode=Create, Overwrite Existing File=false, Write Mode= Use Temporary File. Other terms File...
  5. File Adapter messages stuck in “To Be Delivered” statusSymptom You have upgraded to PI 7.0 SP 18 and you notice that File Adapter messages are stuck in “TBDL”(To Be Delivered) status. Additionally, the following symptoms are noticed: 1 – File...
  6. Temp file remains in directory when file fails with errorSymptom You are using the File Adapter in your business scenario for message processing. During file processing, you notice, that, the temporary file is not deleted(in case file fails with error). The...
  7. Adapter Framework Scheduler may fail to remove a jobSymptom XI Adapter Framework’s scheduler may fail to remove the scheduled job. When this problem occurs, the affected job may get executed continuously for some period in parallel. This problem can be...

Symptom

This note attempts to solve two issues:
a) File sender adapter generates duplicate message IDs and sends it to Messaging system. In the Synchronous(Best Effort) scenario cases, Messaging system does not persist any Message and forwards to Integration Engine. Integration engine checks that this is duplicate and retuns with DUPLICATE_DETECTED error.
b) File sender adapter configured with content conversion and record sets per message feature generates more output files than needed incase of error situations.

Other terms

File adapter,Duplicate message IDs, DUPLICATE_DETECTED, Content conversion
Reason and Prerequisites

Reasons for each of the above cases is as follows:
1) Due to an bug in GUID generator, this occurs rarely on high load multiple cluster environments.
2) Bug in file sender adapter causes this error behavior with content conversion feature.
Solution

1)With this patch, file sender adapter persists the GUIDs in DB table and checks if a message ID is duplicate and then re-generate a new message ID. These entries are persisted for 1 day before they are deleted automatically. Therefore there would no longer duplicate Message IDs.
2)Improvement of re-try logic incase of record sets per message is done with this patch.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment