Hi,

 I tried  running the process with the change you suggested. It seems to be working fine to some extent, i mean now it is able to handle a few files about 4-5, but the problem is still existing as before.

I also observed one more thing :
- The vfsFilePoller component is sometimes failing to pickup the  files from the given directory.
   Say I have just started the esb then it is picking up the files and after some time later
   I put some more files in the polling directory, the vfsFilePoller not picking up them where
   I have left the esb running since my first use.

What do you think, Is this could also be some problem with VFS.

Thanks,
Pavan Kumar


On 12/29/05, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
I'm wondering if the problem comes from our use of commons-vfs.
I recently discovered that commons-vfs has a per thread cache of
streams and this may be the cause of the failure.

Could you try changing your flow to st (just add the flowName="st"
attribute to the xml config for the container)
and let me know what happens ?

Guillaume

Pavan Kumar wrote:

> Hi,
>
> I was trying to use the vfs File Poller component along with vfs
> FileWriter component from
> ServiceMix2.0.2 binary and I also tried these components from
> ServiceMix-2.1-SANPSHOT
> as I have seen some of the bugs in FilePoller component  were fixed
> in  this  version.
>
> The problem I am  facing is with the FileWriter component. When there
> is only one file in the
> polling directory the process of getting the file and writing it to
> the destination directory is
> going on fine, but when there are a bunch of files (say 10 or 15), the
> FileWriter component
> is not able to write correctly and it is  throwing exceptions.
>
> Can somebody help me on this.  The  exception stack trace  is attached
> with this mail.
>
> Thanks in advance,
> Pavan Kumar
>
>------------------------------------------------------------------------
>
>INFO - DeliveryChannelImpl.createExchangeFactory (165) | default destination serviceName for filePoller = {http://servicemix.org/demo/}receiver
>INFO - DeliveryChannelImpl.createExchangeFactory(165) | default destination serviceName for filePoller = { http://servicemix.org/demo/}receiver
>INFO - DeliveryChannelImpl.createExchangeFactory(165) | default destination serviceName for filePoller = { http://servicemix.org/demo/}receiver
>INFO - DeliveryChannelImpl.createExchangeFactory(165) | default destination serviceName for filePoller = {http://servicemix.org/demo/}receiver
>INFO - DeliveryChannelImpl.createExchangeFactory(165) | default destination serviceName for filePoller = {http://servicemix.org/demo/}receiver
>INFO - DeliveryChannelImpl.createExchangeFactory (165) | default destination serviceName for filePoller = {http://servicemix.org/demo/}receiver
>DEBUG - Broker.resolveAddress(373) | Routing exchange [EMAIL PROTECTED] to: ServiceEndpoint[service={http://servicemix.org/demo/}receiver,endpoint=fileSender]
>DEBUG - AbstractFlow.send(117) | Called Flow send
>
>


Reply via email to