FYI, Maybe you already know this.. I report it just in case.... The proxy caching problem is wider that just the timeout. Also deactivating vfs listener proxies doesn't work. (Home > Manage > Service > List > Service Group Dashboard > Service Dashboard -> Deactiviate) The deactivated proxy keeps scanning and handling the files in the directory.
esb version: 2.1 Regards, Harm On Mon, Aug 31, 2009 at 11:47 PM, Harm Verhagen<[email protected]> wrote: > Yes that works around the problem. > Whenever I also change the name, the new polltime is taken into account. > > NB: After that whenever use a name that has been used before, it takes the > _old_ time again of when the name was first used. > > note: I modified time & name by editing the xml in UI -> Configure -> > synapse + hit update after modify. > > > Regards, > Harm > > On Mon, Aug 31, 2009 at 6:56 AM, Evanthika Amarasiri <[email protected]> > wrote: >> >> Hi Harm, >> >> The issue is not with the transport.PollInterval property. The issue is >> with Proxy Services. When you change the poll interval and let it execute, >> it will still read the poll interval specified previously since the Proxy >> services has a caching issue. If you need to let the Proxy Service read the >> new poll interval, you will have to change the name of the Proxy Service >> through 'Manage Synapse Configuration'. Could you please try this out and >> let us know whether it solves the issue? >> >> Thanks, >> Evanthika >> >> On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <[email protected]> >> wrote: >>> >>> It seems esb is reading the timeout somewhere from an internal database >>> instead of from the synapse.xml. >>> Modifying synapse.xml directy in webui doesn't help, changing property in >>> proxy configuration doesnt help. >>> >>> both >>> >>> ./wso2server.bat -DuseSynapseXML >>> >>> ./wso2server.bat --cleanRegistry >>> dont work >>> >>> Any ideas ? >>> >>> Regards, >>> Harm >>> >>> On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <[email protected]> >>> wrote: >>>> >>>> Hi, >>>> >>>> I noticed that a proxy with vfs transport, does not obey the >>>> PollInterval. I set it to 8 here. >>>> It seems however that the files are processed every 30 seconds. >>>> restarting the bus doesn't help. >>>> >>>> I did not overrule the default vfs transport settings in the webUI, Just >>>> specified a proxy. >>>> I expect that any proxy specifiy settings should be used, right ? >>>> >>>> >>>> Is this a known issue ? >>>> >>>> >>>> >>>> synapse snippet >>>> <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true" >>>> trace="enable"> >>>> <syn:target inSequence="sco-input"/> >>>> <syn:parameter >>>> name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter> >>>> <syn:parameter name="transport.PollInterval">8</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.FileNamePattern">.*.xml</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.ContentType">application/xml</syn:parameter> >>>> <syn:parameter >>>> name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter> >>>> </syn:proxy> >>>> >>>> >>>> With the following logs >>>> [2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///home/user/test/in >>>> [2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access >>>> or read file or directory : file:///home/user/test/in >>>> [2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox >>>> [2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///home/user/test/in >>>> [2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access >>>> or read file or directory : file:///home/user/test/in >>>> [2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox >>>> [2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///home/user/test/in >>>> [2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access >>>> or read file or directory : file:///home/user/test/in >>>> [2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox >>>> [2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning >>>> directory or file : file:///home/user/test/in >>>> >>>> This shows every 30 seconds a scan of the directory. >>>> the "//home/user/test/in" seem to come from the default vfs settings >>>> (which I'm not using). >>>> >>>> version: wso2esb: 2.1 on java6, windows xp. >>>> >>>> Regards, >>>> Harm >>> >>> >>> _______________________________________________ >>> Esb-java-user mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >>> >> >> >> _______________________________________________ >> Esb-java-user mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >> > > _______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
