On Sat, Jul 7, 2012 at 6:06 PM, Nirmal Fernando <[email protected]> wrote:
> > > On Sat, Jul 7, 2012 at 6:03 PM, Pradeep Fernando <[email protected]> wrote: > >> Hi, >> >> this issue is in carbon trunk ?? >> > > Yes! > You can reproduce if you set up a carbon-server cluster, in multicast mode and making one server as a group manager (master). Then after slave joins the master, shutdown the slave. You could notice the incorrect ports (without offset) in the master's log related to the leave of the slave. INFO - DefaultGroupManagementAgent Application member Host:10.100.3.105, Port: 4001, HTTP:8285, HTTPS:8243, ACTIVE:true left cluster. >> --Pradeep >> > > > > -- > > 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/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
