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 S
You should not interfere with deployers and deployment using another task,
when your are dealing with deployment synchronizer. The carbon scheduler
task does the job of handling this. Or else you will get into these type of
issues.
BTW, whats the new approach you guys are following to solve this
r
Hi Sinthuja,
On Sat, Apr 12, 2014 at 12:57 PM, Sinthuja Ragendran wrote:
> 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
> too
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
sur
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 seco
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 osgi
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 wrote:
> 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
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. Deployer
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
{org.wso2.carbon.bam.toolbox.deployer.core.
