Hi Urmila
Do you mean an upgrade from ACE 12.0.9 to 12.0.12.7, because going from 9 to 7 would in fact mean a downgrade.
There are a couple of reasons for a broken pipe, most logical one is that some other applications is closing the connections, maybe due to server or network issues.
Do you see this occurring frequently?
If you split up the flow in 30 flows with the shared code in a library, does this solve anything? (You could try this for one flow to see if it works).
If it is due to the ace upgrade and the internal connection reuse, this would be a case for IBM support I believe.
This is an explanation of the actual error: https://www.baeldung.com/java-socketexception-broken-pipe-error
------------------------------
Regards
Matthias Blomme
Integration Specialist
Integration Designers
Turnhout
------------------------------
Original Message:
Sent: Mon February 24, 2025 08:51 PM
From: Urmila V M
Subject: Unknown SFTP Exception on FileInput node
Hello,
I have 2 messages flows in one ACE app to handle files between source and target system.
First message flow which reads from SFTP directory(source) and writes to internal ACE directory.
Second message flow on a scheduled basis reads from internal directory and writes to target system.
These 2 flows were working fine without any issue for almost 2 years, all of a sudden getting below error in 1st flow(FileInput --> FileWrite).
On successful processing of files, it was moved to mqsiarchive. First flow contains 30+ fileinput nodes which reads from same directory connected with different
credentials for different customers. SFTP connection works fine via WinScp but from ACE this error is occurring.
'Unknown SFTP Exception: Session.connect: java.net.SocketException: Broken pipe (Write failed)', '{4}'. \nAn internal software error has occurred in IBM App Conn...
This ACE application is recently upgraded to 12.0.9 from 12.0.7.
------------------------------
Urmila V M
------------------------------