Hi,
i have a problem using the following configuration for fs-listener:
<service category="copy" name="fileCopy" description="copyFtp1" invmScope="GLOBAL">
<property name="maxThreads" value="1"/>
<listeners>
<fs-listener maxThreads="1" name="copyListener" busidref="copyBus" is-gateway="true" schedule-frequency="120">
<property name="composer-class" value="my.composer.LocalCopyMessageComposer"></property>
<property name="file-filter-class" value="my.filter.CommaSeparatedFileFilter"/>
</fs-listener>
</listeners>
<actions mep="OneWay">
<!-- send file via FTP -->
</actions>
</service>
After some day, the service stops working, without an apparent reason.
The listener creates correctly the temp file, but the underlying service doesn't receive the esb-aware message.
Instead, I have another service configured this way, and I haven't had any problem yet.
<service category="copy" name="copy2" description="copyFtp2" invmScope="GLOBAL">
<property name="maxThreads" value="2"/>
<listeners>
<fs-listener maxThreads="2" name="copyListener2" busidref="copyBus2" is-gateway="true" schedule-frequency="120">
<property name="composer-class" value="my.composer.LocalCopyMessageComposer"></property>
<property name="file-filter-class" value="my.filter.CommaSeparatedFileFilter"/>
</fs-listener>
</listeners>
<actions mep="OneWay">
<!-- send file via FTP -->
</actions>
</service>
It can be that limiting to 1 the fs-listener "maxThreads" value causes this problem?
The file size is small (max 15KB) for both services.
Thanks in advance
Giulio
I think the problem is related to the property org.jboss.soa.esb.ftp.timeout set to 0 (infinity), so the single thread hangs forever.
I will try to raise the timeout, 60000 milliseconds can be a good value?