Hi,
Yeah, as Senaka said, it only happens if we go in this specific path, if
you actually log into the mgt-console first, it works correctly, where the
registry is loaded first, observe the following log:-
[2012-10-13 08:41:31,250] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
Server : WSO2 Data Services Server-3.0.0
[2012-10-13 08:41:31,251] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
Carbon started in 18 sec
[2012-10-13 08:41:31,543] INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
: https://192.168.2.135:9444/carbon/
[2012-10-13 08:42:29,994] INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Connected
to mount at sharedregistry in 0ms
[2012-10-13 08:42:30,037] INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Connected
to mount at sharedregistry in 0ms
[2012-10-13 08:42:30,074] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - '
[email protected] [1]' logged in at [2012-10-13 08:42:30,073+0530]
[2012-10-13 08:42:30,114] INFO
{org.wso2.carbon.core.multitenancy.TenantAxisConfigurator} - Creating
tenant AxisConfiguration for tenant: test1.com[1]
************ DEPLOY ************
[2012-10-13 08:42:30,319] INFO
{org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2
service: Test1 {test1.com[1]}
[2012-10-13 08:42:30,342] INFO
{org.apache.axis2.deployment.DeploymentEngine} - Deploying Web service:
Test1.dbs -
file:/media/data/dev/wso2/branches/4.0.0/platform/products/dss/3.0.0/modules/distribution/target/wso2dss-3.0.0-2/repository/tenants/1/dataservices/Test1.dbs
[2012-10-13 08:42:30,444] INFO
{org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -
Permission cache updated for tenant 1
[2012-10-13 08:42:30,910] INFO
{org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} - Loaded tenant
test1.com in 811 ms
Cheers,
Anjana.
On Fri, Oct 12, 2012 at 10:28 PM, Eranda Sooriyabandara <[email protected]>wrote:
> Hi Senaka,
>
> On Fri, Oct 12, 2012 at 9:45 PM, Senaka Fernando <[email protected]> wrote:
>
>> Hi Anjana, Eranda,
>>
>> Actually I had a quick look into this, and I think there is an issue on
>> how this invocation happens. Quoting Anjana,
>>
>> "The following log will explain the scenario, basically it is situation
>> where DSS is started up, and without logging into the mgt-console, we do a
>> direct call to a data service, which will load the tenant and call the
>> deployer."
>>
>> So, whoever loads the tenant does not properly load the registry, which
>> is possibly why we end up running into this situation. Please have a look.
>>
>>
> I'll drill down and see what we can do here.
>
> thanks
> Eranda
> *
> *
>
>
--
*Anjana Fernando*
Associate Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
