Martin,
Could you try to enable DEBUG logging to see what's going on? For SMX4,
the servicemix-file component now uses asynchronous messaging. Perhaps
there's a problem with the locking mechanism we use internally to
determine if a file is already being processed. If this is the case, we
should be able to see this from the DEBUG log, where the same file gets
tried again before the previous MessageExchange for it has ended.
Regards,
Gert
Martin Kuhn wrote:
Edell Nolan wrote:
Hi,
Did you attempt to run this twice on the same file. I have seen issues
before where I had a previous error and this was causing the lock on the
file.
Once I cleaned things up and started servicemix again and then put the
file
into the directory that was being polled it worked fine.
Edell.
Hi,
from my point of view it is a problem with locking but only with SM4 (I
tried the same example with SM3 successfully with no exception).
I reported an error under https://issues.apache.org/activemq/browse/SMX4-121
It would be nice to know what's really going on because I'm a really
frustrated to spend so much time with such a simple use case :-(((
