Hi, Regarding the dispatching issue i was able to fix it by setting HttpSessionDispatcher object to Tenant aware LB Endpoint (when it get initialized). In SLA end point it was handled by DynamicLoadbalanceEndpointFactory. Ideally we have to check session type (soap, http,) and create dispatcher according to it. How do we proceed with this?
Thanks. On Wed, May 2, 2012 at 5:07 PM, Nirmal Fernando <[email protected]> wrote: > Hi All, > > Now we have state replication among load balancers (i.e. primary load > balancer let other load balancers know the current state of it, > periodically (if the state has changed)). I've implemented the algorithm > suggested by Azeez. > > > On Tue, May 1, 2012 at 12:29 PM, Sanjeewa Malalgoda <[email protected]>wrote: > >> This issue happens because dispatchers not getting updated properly for >> request . In the first phase of this project we removed these dispatchers. >> When there are multiple application nodes available this causes to too >> many re directions. will work on this issue. >> Thanks. >> >> >> On Mon, Apr 30, 2012 at 11:37 AM, Sanjeewa Malalgoda >> <[email protected]>wrote: >> >>> As i see issue is with redirecting to node within a cluster. This >>> happens there are multiple nodes available in a cluster. If it is single >>> node it works fine. i'm working on this and update thread soon. This issue >>> is not depend on the auto scaling we have to do something with new >>> endpoint. >>> >>> Thanks >>> >>> >>> On Mon, Apr 30, 2012 at 10:56 AM, Nirmal Fernando <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Apr 30, 2012 at 10:55 AM, Nirmal Fernando <[email protected]>wrote: >>>> >>>>> Hi All, >>>>> >>>>> On Fri, Apr 27, 2012 at 3:09 AM, Sajith Kariyawasam >>>>> <[email protected]>wrote: >>>>> >>>>>> At the time of the demo it was an httpd instance that we could get >>>>>> started inside a newly created LXC, hence couldn't demonstrate the way an >>>>>> LXC joins the Load Balancer. >>>>>> >>>>>> Yesterday we were able to get an app server instance started inside >>>>>> an LXC in the host machine, and then a route was added in the LB machine >>>>>> to >>>>>> enable communication from LB to LXC. (Adding routes in LB is not the >>>>>> agreed >>>>>> approach, but we tried somehow to get the LXC instance registered in the >>>>>> LB) After adding the route, LXC joined the LB successfully, but when we >>>>>> tried to log in to Management Console of the LXC we got some exceptions.. >>>>>> like "Access Denied", "Error occurred while checking registry mode" etc.. >>>>>> >>>>> >>>>> We've performed several tests and concluded that this is some thing to >>>>> do with Tenant Aware LB endpoint and Sanjeewa is already looking into it. >>>>> >>>>> Here's the summary of tests done and there results. >>>>> >>>>> >>>>> *Synapse Dynamic LB Endpoint* >>>>> >>>>> *Tenant Aware Endpoint* >>>>> >>>>> *Without Autoscaling* >>>>> >>>>> √ >>>>> >>>>> X >>>>> >>>>> *With Autoscaling* >>>>> >>>>> √ >>>>> >>>>> X >>>>> >>>>> >>>>> X: having some issues when loading management console, but SOAP UI >>>>> requests get processed without any issue. >>>>> >>>>> >>>>>> Today we will try to find the causes of those exceptions and >>>>>> proceed.. >>>>>> >>>>>> PS : the blocker [1] is resolved now, it was due to a mistake in our >>>>>> data access code. >>>>>> >>>>>> >>>>>> On Mon, Apr 23, 2012 at 6:35 PM, Sajith Kariyawasam >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> As of now Item "1-a" is tested in developer machines, but we are >>>>>>> blocking in testing "1-b" and "2" due to a JDBC dependency issue as >>>>>>> mentioned in [1] >>>>>>> >>>>>>> [1] http://wso2.org/mailarchive/dev/2012-April/003184.html >>>>>>> >>>>>>> >>>>>>> On Thu, Apr 19, 2012 at 10:35 PM, Nirmal Fernando >>>>>>> <[email protected]>wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Herewith I'm sharing the integration plan (phase - 1). Will update >>>>>>>> this document with phase -2 plan ASAP. >>>>>>>> >>>>>>>> >>>>>>>> https://docs.google.com/a/wso2.com/document/d/1EaA-_I1_mjjZKiRJvTYuEZChICBFu2kxUiHX9CBd93A/edit >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Mar 30, 2012 at 4:22 PM, Damitha Kumarage <[email protected] >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi Azeez, >>>>>>>>> When an agent starts up and register in the AgentManagementService >>>>>>>>> it will send the worker node ip , ip of each bride configured in the >>>>>>>>> worker node. When AgentManagementService receive this information it >>>>>>>>> will >>>>>>>>> send it to the Load Balancer. Load Balancer in tern add a rule >>>>>>>>> into it's kernel routing table with Worker node ip as the gateway >>>>>>>>> and bridge ip as subnet to route. >>>>>>>>> I have attached a sequence diagram for this >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Damitha >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Mar 30, 2012 at 2:57 PM, Afkham Azeez <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> The call from Agent to AgentManagementService should be >>>>>>>>>> registerAgent. Not registerWN. >>>>>>>>>> >>>>>>>>>> There is also an autoscaler component in the LB which calls the >>>>>>>>>> AutoscalerService if necessary. >>>>>>>>>> >>>>>>>>>> Also, it is still not clear to me how the route addition part >>>>>>>>>> works. Is that depicted in the diagram? Can we have a few sequence >>>>>>>>>> diagrams >>>>>>>>>> which will show the flows for different cases? >>>>>>>>>> >>>>>>>>>> On Fri, Mar 30, 2012 at 12:46 PM, Damitha Kumarage < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> I have attached herewith a document that detail the things we >>>>>>>>>>> discussed. I think we are now clear on our work items and can >>>>>>>>>>> accelerate the >>>>>>>>>>> developments to achieve first milestone which we would like to >>>>>>>>>>> propose on end of April >>>>>>>>>>> Please go through it and give your feedback ASAP >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Damitha >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> __________________________________________________________________ >>>>>>>>>>> Damitha Kumarage >>>>>>>>>>> Technical Leader; WSO2 Inc. >>>>>>>>>>> Oxygenating the Web Service Platform >>>>>>>>>>> http://www.wso2.com/ >>>>>>>>>>> blog: >>>>>>>>>>> http://damithakumarage.wordpress.com/ >>>>>>>>>>> >>>>>>>>>>> __________________________________________________________________ >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Afkham Azeez* >>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>>> * <http://www.apache.org/>** >>>>>>>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>>>>>> twitter: >>>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>>>> * >>>>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>>>>>> * >>>>>>>>>> * >>>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> __________________________________________________________________ >>>>>>>>> Damitha Kumarage >>>>>>>>> Technical Leader; WSO2 Inc. >>>>>>>>> Oxygenating the Web Service Platform >>>>>>>>> http://www.wso2.com/ >>>>>>>>> blog: >>>>>>>>> http://damithakumarage.wordpress.com/ >>>>>>>>> __________________________________________________________________ >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Dev mailing list >>>>>>>>> [email protected] >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Thanks & regards, >>>>>>>> Nirmal >>>>>>>> >>>>>>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>>>>> Mobile: +94715779733 >>>>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks, >>>>>>> Sajith >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks, >>>>>> Sajith >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Thanks & regards, >>>>> Nirmal >>>>> >>>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>> Mobile: +94715779733 >>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Thanks & regards, >>>> Nirmal >>>> >>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>> Mobile: +94715779733 >>>> Blog: http://nirmalfdo.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> *Sanjeewa Malalgoda* >>> >>> mobile : +94 713068779 >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>> >> >> >> >> -- >> *Sanjeewa Malalgoda* >> >> mobile : +94 713068779 >> <http://sanjeewamalalgoda.blogspot.com/>blog >> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >> > > > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sanjeewa Malalgoda* mobile : +94 713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
