Problem with Append mode in File Receiver

Former Member · ‎06-04-2008

Hello,

I am facing some problem with Append Mode in File Receiver.

In channel config, i have given :

Construction Mode : Append

File Type : Text

Message Protocol : File Content Conversion

The size of the file which i am trying to send is about 9.5MB.

I got this error,

"Recovering from loss of connection to database; message

loaded into queue by recover job: System Job (Failover Recovery)".

So, it would seem that there was a loss of connnection to the database

while the file was being written.

Note - XI successfully recovered from the connection loss and

successfully wrote the file, however since the communication channel

was set to append, it appended to the partial file that was written

before the database connection loss. This is not correct. The file

should have been overwritten after the recovery even though the communication

channel was configured to append.

Can anyone help me on this regard.

Thanks,

Soorya.

former_member537867 · ‎06-04-2008

Hi Venkat,

I would suggest u to split the file in to chunks if u face any problem in processing at a time in append mode and also

Memory Requirements are must 4 processing huge files:

Q: Which memory requirements does the File Adapter have? Is there a restriction on the maximum file size it can process?

A: The maximum file size that can be processed by the File Adapter depends on a number of factors:

o The most important one is the size of the Java heap, which is shared among all messages processed at a certain point in time. In order to be able to process larger messages without an out of memory error (OOM), it is recommended to increase the size of the available Java heap and/or to reduce the concurrency in the system so that fewer messages are processed in parallel.

o Another factor negatively influencing the maximum message size in releases up to and including XI 3.0 SP 13 is an enabled charcter set (encoding) conversion if the message type is set to "Text".

o Using the transport protocol "File Transfer Protocol (FTP)" also uses more memory for processing than the transport protocol "File System (NFS)" (up to and including XI 3.0 SP 13).

o If the Message Protocol "File Content Conversion" is used in a File Sender channel, consider that not only the size of the input file affects the File Adapter's memory usage, but even more the size of the XML resulting from the conversion, which is usually a few factors larger than the original plain text file.

To reduce the memory consumption in this scenario, consider configuring the setting "Maximum Recordsets per Message" for the sender channel. This will cause the input file to be split into multiple smaller mesages.

Plz do refer the following links:

U may plan the availability of ur communication channel using "Planning Availability Times" feature

http://help.sap.com/saphelp_nw04/helpdata/en/45/06bd029da31122e10000000a11466f/frameset.htm

/people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi

hi check the below links for reference

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10748ef7-b2f0-2910-7cb8-c81e7f28...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7086f109-aaa7-2a10-0cb5-f69bd2af...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cc1ec146-0a01-0010-90a9-b1df1d2f...

Regards,

Vinod.