Skip to main content

We have implemented a solution for particular Order Reports -

When the user prints an Order report (say, Project Invoice), the generated PDF has to be uploaded on FTP server and should be attached in the Docman.

For checking in to Docman, we setup the IFS Report Rule Check In To Document Management.

For sending to FTP,  we used the IFS Report Rule - Route to connect, see below -

Route to Connect Configuration

 

This will create an Application message, which we can use to route our PDF report to the FTP server using the below configurations -

 

We added an FTP Connector in Setup IFS Connect like this -

FTP Sender Configuration

 

Then we used Outbound Routing Rule and Routing Address to handle the Application message generated from Report Rule Route to Connect and transfer the file to the FTP server.

Routing Rule Configuration

 

This solution is working fine. The file gets uploaded successfully.

The issue is, when something wrong happens to the FTP server and it refuses to serve or blocks the connection, and user tries to print a report then the application message status stays in Processing and keeps spamming the FTP server to upload the file indefinitely.

How can we limit the number of retries, this solution will do, and after that it will cancel its process of uploading the file to FTP?

If you check above in FTP_SENDER_2 configuration, we used the MAX_RETRIES and other options, but it is not working. Are we doing something wrong?

We are using IFS Apps10 UPD8.

 

Thanks in advance.

We got access to a fraction of FTP logs that shows how 2 file uploads to FTP are continuously looping.

We still can’t figure out what caused them to go in loop in the first place.

 

We checked our Application messages, the file ending with 1000579-1-A1-1.PDF was initiated on 5th Jan’ 22 and the other file 1000584-1-A1-1.PDF was initiated on 6th Jan’ 22.

 

We couldn’t get hands on the logs of 5th and 6th Jan yet, so we can’t figure what was the root cause of this loop.

 

Anyways, my question is still same, how can we limit this solution to execute for a Max no. of retries only.

Our customer had the same issue. During FTP problems application messages were proccesing with neverending loop. It was impossible to check log files because it growing rapidly: 0.5g/few minutes.

Few thousands of application messages retrying on and on. Totally disaster.

Reply


Terms & ConditionsCookie settings