No, this won't work. There are configuration problems. Depends on how you are setting up API-M. If you are setting up the store, gateway, publisher & key manager separately as different clusters, then you need to set the proper ports, and in the case of the gateway, you will need to set the port.mapping ( http://nirmalfdo.blogspot.com/2013/09/why-i-need-portmapping-property-when.html) values as well.
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne <[email protected]>wrote: > Why this comes when API M joins ELB. (ELB local member port 4000) > > [2013-09-12 17:31:35,189] INFO - MemberUtils Added member: > Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: > null, Sub-domain:null, Active:true > > Is this harmless? What needs to be configured for this to work the correct > way? > > -- > *Chamara Ariyarathne* > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; *+94772786766* > -- *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*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
