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 sure that the OSGi service is up before the deployer runs. e.g. [1]
However, I think there is an issue of cyclic dependency if your service is depending on the ConfigurationContextService and won't be able to use this parameter if that is the case. Found this old thread which might be useful in this context [2]. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/event-processor/org.wso2.carbon.event.processor.core/1.0.1/pom.xml [2] http://wso2.com/mailarchive/carbon-dev/2011-October/067499.html Thanks, Lasantha On 12 April 2014 12:57, Sinthuja Ragendran <sinth...@wso2.com> 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 > toolboxes which were not in svn and starting the server? > > If you have the issue with the second case only and first case works fine, > then the reason I pointed out in my last reply would be the cause. > > Thanks, > Sinthuja. > > Thanks, > Sinthuja. > > > On Sat, Apr 12, 2014 at 9:08 AM, Sinthuja Ragendran <sinth...@wso2.com>wrote: > >> 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 >> services are registered and exception thrown during the deployment. >> >> Hence before deploying, the ServerStartUp status being checked by the >> toolbox deployer and if it's not started, then it'll be added to the >> pausedDeployments list. Once the ServerStartup is completed, the >> ServerStartUpInspector which implements ServerStartupHandler from kernal, >> invoke() method is called. And within this method the paused toolboxes >> which were tried get deployed before is getting deployed. >> >> I think in the above case, MessageTracing.tbox is there in BAM by >> default, and during the first startup this toolbox trying to get deployed >> before the server starts, therefore it's getting added to the paused >> deployments list. And before ServerStartupInspector is trying to install >> the paused MessageTracing.tbox (default toolbox), the toolbox deployement >> directory is being cleaned by svn deployment synchronizer and toolboxes are >> being checked out, and hence we are getting error. >> >> >> Thanks, >> Sinthuja. >> >> >> On Sat, Apr 12, 2014 at 8:22 AM, Malith Dhanushka <mal...@wso2.com>wrote: >> >>> 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 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. Deployers should only invoked by the Deployment >>>> Engine. This is not a good design. >>>> >>>> You need to let deployment engine to invoke deployers. Here >>>> the ServerStartUpInspector is invoking the deployers while deployment >>>> synchronizer is checking out the artifacts. >>>> >>>> Thanks, >>>> Sameera. >>>> >>>> >>>> On Fri, Apr 11, 2014 at 9:58 AM, Malith Dhanushka <mal...@wso2.com>wrote: >>>> >>>>> 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.BAMArtifactProcessor} - >>>>> Exception while extracting the BAM >>>>> artifact:/home/wso2/4.2.0/BAM241/cluster/full/10Apr/wso2bam-2.4.1/repository/deployment/server/bam-toolbox/Message_Tracing.tbox >>>>> {org.wso2.carbon.bam.toolbox.deployer.core.BAMArtifactProcessor} >>>>> java.io.FileNotFoundException: >>>>> /home/wso2/4.2.0/BAM241/cluster/full/10Apr/wso2bam-2.4.1/repository/deployment/server/bam-toolbox/Message_Tracing.tbox >>>>> (No such file or directory) >>>>> at java.util.zip.ZipFile.open(Native Method) >>>>> at java.util.zip.ZipFile.<init>(ZipFile.java:214) >>>>> at java.util.zip.ZipFile.<init>(ZipFile.java:144) >>>>> at java.util.zip.ZipFile.<init>(ZipFile.java:115) >>>>> at >>>>> org.wso2.carbon.bam.toolbox.deployer.core.BAMArtifactProcessor.unzipFolder(BAMArtifactProcessor.java:54) >>>>> at >>>>> org.wso2.carbon.bam.toolbox.deployer.core.BAMArtifactProcessor.extractBAMArtifact(BAMArtifactProcessor.java:48) >>>>> at >>>>> org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer.deploy(BAMToolBoxDeployer.java:114) >>>>> at >>>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) >>>>> at >>>>> org.wso2.carbon.bam.toolbox.deployer.internal.ServerStartUpInspector.doPausedDeployments(ServerStartUpInspector.java:49) >>>>> at >>>>> org.wso2.carbon.bam.toolbox.deployer.internal.ServerStartUpInspector.invoke(ServerStartUpInspector.java:35) >>>>> at >>>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:185) >>>>> at >>>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:205) >>>>> at >>>>> org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:282) >>>>> at >>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) >>>>> at >>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >>>>> ....................................................... >>>>> >>>>> For full trace refer[1]. >>>>> >>>>> [1] https://wso2.org/jira/browse/BAM-1558 >>>>> >>>>> Thanks >>>>> -- >>>>> Malith Dhanushka >>>>> Software Engineer - Data Technologies >>>>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>>>> *Mobile* : +94 716 506 693 >>>>> >>>> >>>> >>>> >>>> -- >>>> Sameera Jayasoma, >>>> Software Architect, >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: same...@wso2.com >>>> blog: http://sameera.adahas.org >>>> twitter: https://twitter.com/sameerajayasoma >>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >>>> Mobile: 0094776364456 >>>> >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> Malith Dhanushka >>> Software Engineer - Data Technologies >>> *WSO2, Inc. : wso2.com <http://wso2.com/>* >>> *Mobile* : +94 716 506 693 >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Sinthuja Rajendran* >> Software Engineer <http://wso2.com/> >> WSO2, Inc.:http://wso2.com >> >> Blog: http://sinthu-rajan.blogspot.com/ >> Mobile: +94774273955 >> >> >> > > > -- > *Sinthuja Rajendran* > Software Engineer <http://wso2.com/> > WSO2, Inc.:http://wso2.com > > Blog: http://sinthu-rajan.blogspot.com/ > Mobile: +94774273955 > > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
