Hi, We are planning to add a new parameter called coordination. (default value is true)
When the coordination is true, ESB will use NTASK to run the pooling protocol. (Given time one node. In cluster given time one worker node) When this is set to false ESB will be using a background thread to run the polling protocol. (Given time all nodes. In cluster given time all worker nodes) eg: <inboundEndpoint xmlns="http://ws.apache.org/ns/synapse"; name="file" sequence="request" onError="fault" protocol="file" suspend="false"> <parameters> <parameter name="interval">10000</parameter> *<parameter name="coordination">true</parameter>* <parameter name="sequential">true</parameter> <parameter name="transport.vfs.FileURI">/home/user/work/inbound/vfs/new</parameter> <parameter name="transport.vfs.ActionAfterFailure">NONE</parameter> <parameter name="transport.vfs.ActionAfterProcess">NONE</parameter> <parameter name="transport.vfs.ActionAfterErrors">NONE</parameter> <parameter name="transport.vfs.Locking">enable</parameter> </parameters> </inboundEndpoint> On Wed, Dec 3, 2014 at 11:07 AM, Malaka Silva <[email protected]> wrote: > Hi All, > > I had a offline discussion with Anjana. Currently the NTask will run in > one node at a given time. > > But as we develop the inbound we have the requirement to either run on all > nodes, limited nodes or single node. > > We are currently discussing this internally, how we can achieve this for > inbound. > > One way is we can use NTask if we require coordination. In other cases we > can simply do the polling using a background thread. > > Best Regards, > Malaka > > On Fri, Nov 28, 2014 at 11:44 AM, Anjana Fernando <[email protected]> wrote: > >> Hi Malaka, >> >> Yeah, we can, for each task, we can give a "TaskLocationResolver", where >> it determines the candidate locations for the task to be scheduled in. >> Globally, this can be controlled in the tasks-config.xml, where we have a >> "defaultTaskLocationResolver", this is used, if we don't internally give an >> explicit TaskLocationResolver. >> >> Cheers, >> Anjana. >> >> On Fri, Nov 28, 2014 at 10:12 AM, Malaka Silva <[email protected]> wrote: >> >>> Hi, >>> >>> Is there a way to set the coordination behavior in NTask. (All or one >>> worker) >>> >>> If so can we do this for each task or global setting? >>> >>> Best Regards, >>> >>> Malaka Silva >>> Senior Tech Lead >>> M: +94 777 219 791 >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> http://www.wso2.com/ >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> >>> Save a tree -Conserve nature & Save the world for your future. Print >>> this email only if it is absolutely necessary. >>> >> >> >> >> -- >> *Anjana Fernando* >> Senior Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > > Best Regards, > > Malaka Silva > Senior Tech Lead > M: +94 777 219 791 > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > > Save a tree -Conserve nature & Save the world for your future. Print this > email only if it is absolutely necessary. > -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
