i running poller inside inbound-channel-adapter . noticed differences in execution when poller has cron attached:
int:poller cron = 0 */10 * * * *
expected poller loads, picks files available in directory provided , tries again after 10 minutes:
on windows - files picked available no matter count , next execution comes after 10 minutes.
on unix - takes 10 minutes poll each file. if first file polled 09.00 , next polled 09.10 on windows, @ 09.00 files picked , again @ 09.10.
is expected behavior?
your terminology isn't clear me.
anyway: filereadingmessagesource scans target directory files or on each poll or when internal queue<file> tobereceived empty (on poll, too, of course). sourcepollingchanneladapter has maxmessagesperpoll option, 1 default. so, each poll task picks 1 file memory , sends channel. , yes, after polling interval next 1 emitted.
you can configure maxmessagesperpoll = 0 , files in tobereceived send channel during 1 polling cycle.
see polling message source more information.
