On Mon, May 7, 2012 at 10:06 PM, Charitha Kankanamge <[email protected]>wrote:
> Why should we enable axis2 clustering in order to get registry based > deployment synchronizer working? This might be due to the improvements Azeez implemented recently. Basically we use the clustering group comm mechanism to pass events among the nodes and these events fire the synchronizer activities. Thanks, Hiranya > > > On Monday, May 7, 2012, Subash Chaturanga wrote: > >> >> >> On Mon, May 7, 2012 at 2:19 PM, Charitha Kankanamge <[email protected]>wrote: >> >>> Has anyone got registry based deployment working with C4 alpha packs? I >>> tried with setting up a 2 node ESB cluster with registry based synchronizer >>> but it does not seem to work. The artifacts are synchronized across cluster >>> nodes only if the nodes are restarted. >>> >>> >> Hi Charitha, >> I was able to get this working on C4 alpha packs. >> I also setup a two node master slave ESB cluster with a shared registry >> which runs on mysql (*without using the admin console). >> >> But with the given instructions to reproduce this in the >> CARBON-13044<https://wso2.org/jira/browse/CARBON-13044>, >> I also could not get this working. Because the clustering should be enabled >> in the axis2 level. >> With that I got deployment sync working. >> >> (The UI seems to be broken and gives me exceptions (and thus I did it >> from xml configs), but still it shows that the deployment sync created). >> Did you enabled clustering in axis2.xml ? >> >> [1]https://wso2.org/jira/browse/CARBON-13044 >>> >>> Please have a look at this and resolve if there is a bug. This is very >>> important for us to proceed with production test setups. >>> >>> /Charitha >>> >>> ---------- Forwarded message ---------- >>> From: *Kasun Gajasinghe* <[email protected]> >>> Date: Wed, Apr 25, 2012 at 8:34 PM >>> Subject: Re: https://wso2.org/jira/browse/CARBON-12801 >>> To: Hiranya Jayathilaka <[email protected]> >>> Cc: Charitha Kankanamge <[email protected]>, Dimuthu Leelarathne < >>> [email protected]>, Afkham Azeez <[email protected]>, support-dev-group < >>> [email protected]> >>> >>> >>> >>> >>> On Wed, Apr 25, 2012 at 12:23 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>> >>> >>> On Tue, Apr 24, 2012 at 6:13 PM, Kasun Gajasinghe <[email protected]>wrote: >>> >>> >>> We should find a way to resolve the conflicts. Current implementation >>> doesn't support conflict resolving. As I found out, for svn-based depsync, >>> the svn conflict resolver is not implemented in Svnclient. >>> >>> >>> It is implemented. >>> >>> >>> >>> Let me clarify what I meant to say. Yes, 'resolved' subcommand is >>> implemented. Though it's deprecated in favor of 'resolve' subcommand, the >>> functionality is there. What's not there is a way to resolve conflicts *the >>> moment it happens in commandline adapter*. There's a callback >>> functionality implemented (DefaultConflictResolver), but this callback >>> isn't used because the underlying methods are marked as TODO. >>> >>> >>> I think this should be implemented, or bring in a new underlying >>> dependency for Svnclient like svnkit instead of current CommandLine >>> adapter that already has the needed implementation. >>> >>> >>> We can't take a dependency on SVN Kit and redistribute it due to >>> licensing matters. But SVN client adapter allows you to use SVN Kit as a >>> drop-in. That's what we do in SLive. >>> >>> >>> Yes, the license is a problem. Seems they are using a custom license >>> called TMate license. In this case, the ideal path is to implement the >>> needed implementation for commandline adapter. The code seems to be easy to >>> understand as well. I believe there must be a way to automatically resolve >>> conflicts because when that happens, that node can no longer commit. And, >>> when there's xml files, the structure is broken because svn adds content >>> like the following to conflicted xml files. >>> >>> >>>>>> .mine >>> --- >>> <<<<< >>> --- >>> >>> Thanks, >>> --KasunG >>> >>> Thanks, >>> Hiranya >>> >>> >>> _______________________________________________ >>> >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Subash Chaturanga >> Software Engineer >> WSO2 Inc. http://wso2.com >> >> email - [email protected] >> phone - 077 2225922 >> >> > > -- > Charitha Kankanamge > cell: +94 718 359 265 > blog: http://charithaka.blogspot.com <http://wso2.com> > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
