On Tue, Jun 12, 2012 at 6:14 PM, Kathiravelu Pradeeban <[email protected]>wrote:
> Hi, > I created a tenant (tenant id = 1) in my Appserver trunk build, and > deployed a service from the tenant. But the service goes into the super > tenant space repository/deployment/server/axis2services and not into > repository/tenants/1/axis2services. I log in as the super tenant, and the > service was available there. > > Then I restarted the server, and logged in as the tenant which initially > uploaded the service. The service is no more there (That I expected as > well, since this indeed got deployed into the super tenant space). > > I found this issue, when debugging the usage publishing code. Is this > issue fixed already or someone working on it if this issue known, as this > is a critical issue? > The root cause here is the tenant ConfigurationContext separation is broken. There is a handler (ActivationHandler) which is responsible for loading the correct tenant's ConfigurationContext. This handler contacts the SuperTenantCarbonContext to get the current tenantId. Using this tenant Id only, it loads the tenant specific configuration context. But for some reasons the tenant id returned form CarbonContextHolderBase is always -1234, which is the id of ST. This is why for all tenants, the ConfigurationContxt of ST is being used, which is wrong. Kishanthan. > > Thank you. > Regards, > Pradeeban. > -- > Kathiravelu Pradeeban. > Cloud Technologies Team. > WSO2 Inc. > > Blog: [Llovizna] http://kkpradeeban.blogspot.com/ > M: +94 776 477 976 > > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
