This content has been marked as final. Show 4 replies
however, we observe that the input edi file is picked sometimes successfully and sometimes with failure..What error do you see? Can you post the stacktrace from server log?
b2b.edi.enablePreprocess only removes the unwanted leading/trailing CRLF's from the EDI file so it will not impact any data.
There should not be any issue w.r.t cluster.
Just ensure to restart the server after adding the property.
It could be a case that the file would have been copied partially when polling listening channel. Try increasing the polling interval and see.
If the issue persists, please send the diagnostic log in trace:32 mode to my email-id (in my profile)