| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem using Fileinput node (getting uncomplete files) |
« View previous topic :: View next topic » |
| Author |
Message
|
| ninja |
 Posted: Fri Dec 11, 2009 2:29 am Post subject: Problem using Fileinput node (getting uncomplete files) |
 |
|
Newbie
Joined: 21 Jul 2009
Posts: 8
|
Hi all,
I'm developing for the first time flows using FileInput/FileOutput nodes (using WMB 6.1) and I have the following problem: my flow has to process an XML file which is transferred via FTP.
Since the ftp application doesn't put a file lock, my flow sometimes starts processing a partial file and, obiously, doesn't process the file correctly exiting with an XML parsing error.
Moreover, when this unlucky event occurs, the flow doesn't process any file any longer, even the ones arrived later: then you have to restart the flow.
I tried to limit this problem raising the polling time but I know this is not the good solution.
Do you know how to face this problem?
Thanks in advance. |
|
| Back to top |
|
 |
| nathanw |
| Posted: Fri Dec 11, 2009 2:57 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
techinically this is not th fault of the node or even WMB
change the FTP program to lock until complete
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| ninja |
| Posted: Fri Dec 11, 2009 3:08 am Post subject: |
|
|
Newbie
Joined: 21 Jul 2009
Posts: 8
|
Unfortunately this is not possible: I don't have any control on the file transfer application and who manages that application said that they can't put file lock.
So I need to find a solution for that inside WMB flows. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Fri Dec 11, 2009 3:36 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Are you using the Fileinput node Retry tab to define how retry processing is performed when the message flow fails?
AFAIK the should not stop processing unless you do not have the appropriate retry and backout processing in place. If you know roughly how long the ftp application will take to write the file you should be able to configure the retry interval and number of attempts to avoid most problems.
But you should highlight the lack of locking as a risk to the project so that when it becomes an issue it is not blamed on the flow... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
