L.S.,
What version of ServiceMix are you using? Prior to ServiceMix 3.3, the
file poller was using synchronous message exchanges which can more
easily lead to polling threads being blocked waiting for something else
to happen. You can figure this out by connecting to your ServiceMix
instance with a JMX console and looking at the stacks for all the
threads. If most of your file components threads are WAITING, just post
us the stacks so we can help you figure out what needs to change.
Regards,
Gert
Char wrote:
Hello,
we are using the jbi:file component to poll a huge amount of files. In a
test szenario, i am deploying 2000 small files, which are polled correctly.
When i deploy another 2000 files, a lot of them (300-500) seem to be ignored
by the filepoller.
Behaviour: You can still delete them, so there is no lock on them. If you
deploy more files, the newer ones are being polled, whereas overwriting the
sticky ones does not help.
Test-Setup: 2000 files with different file names. 2nd deploy with same
filenames.
Configuration:
<file:poller service="FilePoller"
endpoint="FileIn"
targetService="InboundRoutingService"
targetEndpoint="FileInEndpoint"
file="../Data/Inbound/FileIn"
autoCreateDirectory="false"
period="5000"
archive="../Data/Inbound/Archive">
<!-- Custom Marshaler, if you are not going to poll xml files.
-->
<property name="marshaler">
<bean
class="org.apache.servicemix.components.util.BinaryFileMarshaler" />
</property>
</file:poller>
Any ideas how i can analyse this behaviour?
thx in advance
