File adapter recovery and exactly once processing

[Former Member]

When we have 1 file with let's say 30 lines (input) this results in 30 messages to XI.

When during the processing of the file the system crashes (which we did on purpose)

The systems want to process line 12 again although it is already in the XI integration server.

See log below:

I have noticed from the trace file information that files which are not processed completely is written in: C:XI_Adapters ech_adapterData ArnhemSalaryData_inbound_ID.dat.

I would like to know if any one knows how to tell the file adapter that line 12 is already correctly processed.

Otherwise I can only change the current input file and delete line 1-12. Then the file will be processed but it is treated as a completely new file.

L O G F I L E

-

-

---

Nov 5, 2003 12:28:12 PM ...i.messaging.adapter.File2XMBProcessor Info: In 'C:/XI_Testfiles/Arnhem_Test/Input': 1 file(s) found that meet file filter '.' with attribute 'R'

Nov 5, 2003 12:28:12 PM ...i.messaging.adapter.File2XMBProcessor Info: C:XI_TestfilesArnhem_TestInputArnhem_test.txt

Nov 5, 2003 12:28:12 PM ...i.messaging.adapter.File2XMBProcessor Info: Process file 'C:XI_TestfilesArnhem_TestInputArnhem_test.txt' with size 2696, timestamp 20031030100113 as text file in 'exactly once' mode

Nov 5, 2003 12:28:12 PM ...i.messaging.adapter.File2XMBProcessor Info: Get key 'Arnhem_test.txt___2696___20031030100113' with message GUID '7c49aba1-0ab9-11d8-8d07-e6a60aa31113' from DB

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: Structure conversion plain->xml entered: continue with line 13 document conversion

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: IIIEK - line number 13 <> 12 - recover mode activated

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: Recovery - starting with line 12,

content '92003088000808149900000005323992'

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: Fix recordset structure assume row type 'ArnhemSalary'

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: Fix recordset structure assume row type 'ArnhemSalary'

Nov 5, 2003 12:28:12 PM ....sap.aii.messaging.adapter.Conversion Info: Successful message conversion (containing 1 recordset(s)) with 1 structures, constructed from ln.no. 12 to 12, return with 'to be continued', token 13

Nov 5, 2003 12:28:12 PM ...messaging.adapter.IntegrationServerIO Info: Sending message '7c49aba10ab911d88d07e6a60aa31113' to Integration Server...

Nov 5, 2003 12:28:12 PM ...messaging.adapter.IntegrationServerIO Error: Sending message '7c49aba10ab911d88d07e6a60aa31113' to Integration Server failed with 'PROTOCOL.MSGID_EXISTING_INBOUND': 'Message ID 7C49ABA10AB911D88D07E6A60AA31113 for pipeline CENTRAL already exists in called system', context '' , must retry

Nov 5, 2003 12:28:12 PM ...i.messaging.adapter.File2XMBProcessor Error: Error sending document of file 'C:XI_TestfilesArnhem_TestInputArnhem_test.txt':

com.sap.aii.messaging.net.TransportException: Sending message '7c49aba10ab911d88d07e6a60aa31113' to Integration Server failed with 'PROTOCOL.MSGID_EXISTING_INBOUND': 'Message ID 7C49ABA10AB911D88D07E6A60AA31113 for pipeline CENTRAL already exists in called system', context '' , must retry

- quit this run, wait for retry

[Former Member]

Theo,

I have seen the same message. I believe this is related to how you start the adapter after the crash. If you click "Start" you may get this message. If you click "Restart" it picks up where it left off. From what we have seen if the adapter is on Automatic start it will startup and work correctly also.

Regards,

Paul Conner

[Former Member]

Hi Paul,

thanks. I think this might be the case.

We don't have the adapter on automatic start yet, because we are testing, so we use a Start.

When I am at the customer site again I will try your suggestions.

Regards,

Theo

[Former Member]

Extra info. It is a known problem which will be solved in SP 4.

It should be available in the next weeks.

Regards,

Theo

[former_member282368]

Theo,

I would be interested to see your adapter configuration. We've had this exact same situation, but what we see happen is the adapter start up where it left off in the file. When it gets the suplicate message error back from the integration server, the adapter then goes on to the next message. Are you using 'EOIO' or 'EO' mode?

Regards,

Chris

[Former Member]

Hi Chris,

on monday I will be at the customer site again, so I can not give the exact configuration right now.

But I know we are using the EO mode.

Regards,

Theo

[Former Member]

Hi,

to guarantee the exactly once handling in case of crashes, the file adapter stores the number of messages which have already been sent to the XI Server at runtime.

When restarting after the crash, the adapter picks the file again and continues to sent with the next single message to the xi server.

Best regards

Holger