2. Let says, the JBoss ESB server is currently stopped and i deposit a new file called "hello.dat" into the ftp server. Now i start the server and run the example, this "hello.dat" is not pick up.
Well this would simulate a situation where all your servers are shutdown for some reason. If you were to restart them, all files that are on the remote readonly ftp server will be picked up and processed again, which might not be desirable.
The cache contains the filenames that have been picked up and the amount of time that they are held in the cache can be configured with an eviction policy.
Are you seeing this behavior with a file that has not been pickup by before?
Yes, i see the situation with a new file that has not been pickup before.
A typical case would be like this:
The remote FTP server is a separate system, and is continuously being updated with files (.dat). Our ESB app server would pickup these files for processing. Sometimes the ESB app server may need to be shutdown for maintenance/upgrade. These would create a case of ESB app restart and within that time period, the remote FTP server may be added with new files.
I did my testing with the remote FTP server on my laptop, not sure if this affect the outcome.
Btw, i saw the treecache was being synchronise with the remote FTP file list, after the app is deployed.
Did you see a similar result as i did?
Which version of JBossESB are you running?
I'll take a look at this and see what the results are. Might not be until tomorrow though.
Sorry for not responding early, i was recovering from flu :(
I am using the latest ESB build, 4.3 GA.
Thanks for the help.
nps, and sorry about my late reply on this. Have been on holidays plus have some other issues that I need to see to at the moment.
But I will get around to this and try to help you out. Sorry about this.