Need your opinion on the error thrown in reverse invoke server while transferring a file(transferred through FTPS by an external system) through HTTP to internal server.
[ISS.0053.0006C] (tid=807,284,766) Unable to forward request to internal server due to error: Read timed out
followed by
[ISP.0090.0003C] Queuepush failed for file
What has been done so far :watt.net.timeout parameter is doubled from 60 sec to 120 sec in internal server and Max No. of threads in internal server registration ports are doubled from 5 to 10.
Size of the file for which the error was thrown is around 11 MB. (Even 26 MB file got transferred successfully earlier). What may be the reason for this? Appreciate your help on this.
Thanks for the suggestion, will try that. One question regarding EDIINT MDN, getting below error in TN activity log: “MDN Disposition: automatic-action/MDN-sent-automatically; processed/error: unexpected-processing-error”.
Client getting errors like: One was “The receipt was unsigned”, the other was “The Message ID returned by the server does not match”. Any suggestions on how to check this?
Yes, MDN is sent signed. Our system receives and sends out MDN, there is no outbound communication. One more error partner is getting: “The Message Integrity Check returned by the Server is incorrect”. But I don’t see any errors in server logs and in TN, the file sent by partner is received with status message: “System status is DONE; user status is ProcessMsg:PAYLOAD”
MDN: “System status is DONE; user status is SendMDNMsg:DONE”
Error indicates problem could be with the certs or network security issue while transmitting/Decrypting the MDN payload. Please do search on the Empower also.
You may need to work with the TP and troubleshoot it…I have seen these type of funky errors and some times it works and not works due to changes in the environment or network changes we never know.
But what did your TP says?..Is this issue in production setup?
Since no errors reported in server side, it is kind of wild goose chase. TP is checking on his side for errors on his side if any. It is pretty much clear on server side.