Skip to Content
author's profile photo Former Member
Former Member

Problem with FTP Sender adapter. IOException: Stream closed

Help. I'm in big trouble.

If my "flat"-file have few records its no problem, but if the file have more than ca. 60 - 70 records I got the error described below.

If I split the file in several small files everything is all right .

The adapter is an FTP with FCC protocol.

Could this be an memory-problem?

<b>Sender Adapter v2024 for Party '', Service 'YX':

Configured at 2007-11-29 16:39:19 CET


- 2007-11-29 16:39:19 CET: Retry interval started. Length: 60,000 s

- 2007-11-29 16:39:19 CET: Error: Conversion of complete file content of 'PDTYXENER.DAT.20071129160053.000611' to XML format failed around position 0: IOException: Stream closed

- 2007-11-29 16:39:19 CET: Processing started


My inputfile have this structure.:


B0000020H060000021199 N2007112811270000654001000009000540006599330000062305

C0000030H0600000211990000115162030003021000000300100000025310000710 83880000654002

C0000040H0600000211990000115162040004023000000399900000033700000780 83880000654002

C0000050H0600000211990000115306010005062000000500000000037150000500 73510000654002

C0000060H0600000211990000115306050005061000000500000000037150000510 73510000654002

C0000070H0600000211990000115306060006073000000600000000044570000520 73510000654002

C0000080H0600000211990000115311010005075000000499900000037650000240 74290000654001

C0000090H0600000211990000115311020003047000000299900000022600000190 74290000654001

C0000100H0600000211990000115311030002032000000200000000015070000200 74290000654001

C0000110H0600000211990000115311040003048000000300000000022610000190 74290000654001

C0000120H0600000211990000115311050004065000000400100000030150000190 74290000654001

C0000130H0600000211990000115311020002030000000200000000015060000260 74290000654002


B0001020H060000021201 N2007112812150000631001000009000540006599330000000001

C0001030H0600000212010000107074010003028000000299900000024210000460 80060000631001



C0001060H0600000212010000115125030003023000000300000000025440000610 84280000631001



C0001090H0600000212010000115125040003020000000300000000025420000690 84280000631001



C0001120H0600000212010000115208020002015000000200000000017200000590 85490000631001





This example will be mapped to two iDocs.

i.e B-E is the iDoc

I will be very happy if someone could help me.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 07:09 PM

    HI Carlsen,

    As it is related with FTP only can consult the FTP side.

    this type of exception rises due to some input entry throws it.

    In you case it is due to large size of the message.So this has closed the stream.

    The code queries a

    table that stores a file in an image column. On some systems this exception

    is thrown intermittently; for some records this query fails 1 of 8 times,

    sometimes it fails 7 of 8 times. It seems like there is less of a problem

    with smaller image fields, <MAX set KB, and more of a problem with larger values

    >1MB. The exception is thrown after some data is read from the stream as

    noted later in this description.

    you can suggest the FTP side to set s supertype to handle this exception

    Or tell them to icrease the Max size limit of the FTP Server.

    **PS: reward points if useful**


    Sumit gupta

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 04:30 PM

    This is a issue with FTP server,looks to me that when u try to fetch a large file it somehow timeouts and closes the I/O stream but in case of small file it doesn't

    its not a problem with XI but with the FTP server.

    get in touch with the FTP server guys



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.