On Mon, Apr 26, 2010 at 10:32 PM, Anjana Fernando <[email protected]> wrote:
> Hi, > > Yeah, got it. I checked which AxisObserver objects are added to the > observer list in AxisConfiguration, and they are in the following > order, > > * org.wso2.carbon.core.deployment.DeploymentInterceptor > * org.wso2.carbon.security.deployment.SecurityDeploymentInterceptor > * org.wso2.carbon.sts.STSDeploymentInterceptor > > The first two gets added before any services/modules are getting > deployed. Where as the "org.wso2.carbon.sts.STSDeploymentInterceptor" > gets added after modules/services are deployed, and I guess sometimes, > while they are getting deployed. So seems the registering of > "STSDeploymentInterceptor" needs to be looked at. > Yes. Please have a look at the SecurityDeploymentInterceptor class. An instance of this class is registered as an OSGi service before the carbon core bundle gets activated (before the initialisation of Axis2). This service registration is perfomed by Declarative services engine. We need to update the SecurityDeploymentInterceptor using the same method. Thanks Sameera > > Cheers, > Anjana. > > On Mon, Apr 26, 2010 at 8:59 PM, Afkham Azeez <[email protected]> wrote: > > Please debug and find out all the AxisObservers in the system, once the > > server has properly started, and then we can check each Observer one by > one. > > We have only a handful of AxisObservers so this should be easy. > > Azeez > > > > On Mon, Apr 26, 2010 at 6:57 PM, Anjana Fernando <[email protected]> > wrote: > >> > >> Hi, > >> > >> I'm getting the following [1], while a service is being deployed by > >> the data services deployer. This occurs because some AxisObservers are > >> added while the observers list already registered is being iterated. > >> This should not happen since, when a service is deployed, all the > >> AxisObserver should be already registered. > >> > >> As verified by Sameera, Carbon has the functionality to register > >> AxisObservers before any module or service is deployed. It can be > >> possible that someone has registered an AxisObserver using another > >> approach rather than the recommended way. Please verify such code who > >> registers AxisObservers. > >> > >> [1] - http://pastebin.com/NB5U6ddB > >> > >> Thanks, > >> Anjana. > >> > >> -- > >> Anjana Fernando > >> Software Engineer > >> WSO2, Inc.; http://wso2.com > >> lean.enterprise.middleware > >> > >> _______________________________________________ > >> Carbon-dev mailing list > >> [email protected] > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > > Afkham Azeez > > Software Architect & Product Manager, WSO2 WSAS; WSO2, Inc.; > > http://wso2.com, Lean . Enterprise . Middleware > > Member; Apache Software Foundation; http://www.apache.org/ > > email: [email protected] cell: +94 77 3320919 > > blog: http://blog.afkham.org > > twitter: http://twitter.com/afkham_azeez > > linked-in: http://lk.linkedin.com/in/afkhamazeez > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > Anjana Fernando > Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
