Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi Sinthuja, On Sat, Apr 12, 2014 at 12:57 PM, Sinthuja Ragendran sinth...@wso2.comwrote: Hi Malith, To confirm can you delete all the toolbox from deployment/server, and including .svn directory, and start the BAM node? And do you still see this problem? Or you get this when you have

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi, As per the off line chat with Kishanthan we have identified 3 possible options to solve this. 1 Delay the axis2 startup until BAMToolBoxDeployer get resolved (need to check for cyclic dependencies) 2 Delay the deployer registration of BAMToolBoxDeployer until its dependencies get resolved 3

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi all, Can't we use the 'Axis2RequiredServices' to make sure that toolbox deployment happens only after the service is registered? CEP has a similar requirement for all components that have a deployer and after discussing with carbon team, we found out that we could use this parameter to make

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi Sameera, Noted and thanks for the explanation. Will refactor the design correctly. Thanks On Fri, Apr 11, 2014 at 11:48 PM, Sameera Jayasoma same...@wso2.com wrote: AFAIK, DepSync doesn't work in this manner. DepSync first get a checkout. Once that is completed it tries to deploy. I

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi, The toolbox will be deployed once the server is properly started up, this is because it uses the osgi services to deploy the toolbox. Since there is no dependency between osgi service registration and toolbox deployment, in past we have experienced the toolbox is starting to deploy before

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

Hi Malith, To confirm can you delete all the toolbox from deployment/server, and including .svn directory, and start the BAM node? And do you still see this problem? Or you get this when you have default toolboxes which were not in svn and starting the server? If you have the issue with the

[Dev] Possible Dep sync issue in BAM toolbox deployment

Hi folks, We noticed following exception in dep sync enabled BAM clustered set up. It seems node1 is trying to deploy a tbox while checking out the same tbox from management node. Is it a possible behavior? TID: [0] [BAM] [2014-04-11 18:49:57,125] ERROR

Re: [Dev] Possible Dep sync issue in BAM toolbox deployment

AFAIK, DepSync doesn't work in this manner. DepSync first get a checkout. Once that is completed it tries to deploy. I guess you guys are doing something wrong here :). Let me explain. By looking at the exception stack trace, I can see that ServerStartUpInspector is invoking deployers.