| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Multiple Transferes triggered at the same time |
« View previous topic :: View next topic » |
| Author |
Message
|
| matuwe |
 Posted: Thu Jul 24, 2014 12:50 pm Post subject: Multiple Transferes triggered at the same time |
 |
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Hi, I have just installed MFTE7.5.2 loving it.. But I am experiencing strange problems that I never had on FTE 7.0.3. If 20 files are saved at the sametime into my monitor directory, 20 monitors are triggered all having 20 transfers to do, thus locking each other out.
Am I not supposed to have 1 monitor triggered with all 20 files in the transfer, or have 20 monitors each with 1 file to transfer?   .
What could I have done wrong.. I am using the same agent properties as on 7.0.3 |
|
| Back to top |
|
 |
| tomleend |
| Posted: Mon Jul 28, 2014 1:10 am Post subject: |
|
|
Acolyte
Joined: 24 Jan 2014
Posts: 51
|
Hi matuwe,
It sounds to me like you've fallen into the classic trap of using wildcards in both the resource monitor's trigger condition and within the transfer request XML associated with the transfer.
From the Infocenter:
"Do not create a monitor that monitors for *.zip, and then transfers *.zip. The monitor tries to start a transfer of *.zip for every .zip file on your system. That is, the monitor generates * number of transfers for *.zip."
http://pic.dhe.ibm.com/infocenter/wmqfte/v7r0/topic/com.ibm.wmqfte.doc/resource_monitoring.htm
So, as an example, say you have a resource monitor that triggers on the wildcard pattern "*.txt" in the directory /home/matuwe/transfers. If you drop 20 .txt files into this directory (file1.txt, file2.txt ... etc) then when the resource monitor polls, it will trigger 20 times (as there are 20 files satisfying the trigger condition). With the default batch size of 1, this will result in 20 managed file transfer requests submitted to the agent. If each managed file transfer request is then configured to transfer *.txt, then each of the twenty transfers will match and try and transfer each of the 20 .txt files.
To resolve this, use variable substitution.
Have your resource monitor poll for *.txt and then transfer ${FilePath}. This way the file that triggered the resource monitor will be the one that is transferred by the request that is submitted.
You can also increase the batch size such that the number of files to transfer per request is equal to the value of the batch size (this can reduce the number of individual file transfers).
Variable substitution and configuring the batch size on a resource monitor is all well documented in the Infocenter / Knowledge Center should you need a reference.
I hope this helps! |
|
| 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
|
|
|
|
