Posted: Thu Feb 23, 2012 12:09 am Post subject: FileInput and JCN node behavior
Acolyte
Joined: 26 Oct 2005 Posts: 65
Hello guys. I have couple of doubts.
1. We have pretty large file over 50 MB coming in from remote location in a local directory where FileInput node listens. Due to some reasons it takes a while to complete this file transfer process and we have observed that before file is completely copied,our fileInput node picks the file and starts processing it. Is it expected behavior? (we are on WMB 6.1.0.4)
2. Regarding JavaComputeNode, does it support multithreading? I mean if I have 10 instances running of a message flow which contains JCN, can the java code run concurrently?
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
perhaps you should consider writing the file to a different directory and then moving it (once the write is complete) to the directory where the FilInputNode will pick it up?
This point has been discussed before in this forum.
Regarding your second point, this again has been discussed here before.
Did you search for the previous posts? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Posted: Thu Feb 23, 2012 5:37 am Post subject: Re: FileInput and JCN node behavior
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
sanjoo wrote:
We have pretty large file over 50 MB coming in from remote location in a local directory where FileInput node listens. Due to some reasons it takes a while to complete this file transfer process and we have observed that before file is completely copied,our fileInput node picks the file and starts processing it. Is it expected behavior? (we are on WMB 6.1.0.4)
Write yourself a little Java app that reads a file. Start the file transfer going and before it's finished start your app running. You'll notice that it doesn't wait for the file to be completely copied before it reads it in. That's because your app doesn't know the file is incomplete. The FileInput node doesn't know for the same reason. _________________ Honesty is the best policy.
Insanity is the best defence.
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