On Tue, May 28, 2013 at 5:05 AM, Dimuthu Leelarathne <dimut...@wso2.com>wrote:
> Hi Shamika,
>
> Did we try to put logs in "private static ConfigurationContext
> createTenantConfigurationContext" in TenantAxisUtils ? We need to put debug
> logs along the path and see what takes all the time?
>
+1, this will reveal the culprit. In fact, we've noticed same happens in AS
as well, so this could be a Carbon level issue, not an ESB specific one.
>
> thanks,
> dimuthu
>
>
> On Tue, May 28, 2013 at 2:38 AM, Shamika Ariyawansa <sham...@wso2.com>wrote:
>
>> Hi,
>>
>> Following observation was made wrt the ESB 4.6.0 instance which was
>> spawned from the S2 ESB cartridge.
>>
>> 1. When the tenant user is logged for the first time the page keeps on
>> loading and after few minutes the page gets timeout
>> Refer the following log.
>>
>> TID: [0] [ESB] [2013-05-27 06:10:16,510] INFO
>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder} - Get
>> the tenant ( tenant id=142) detlail.
>> {org.wso2.carbon.appfactory.userstore.AppFactoryRealmConfigBuilder}
>> TID: [0] [ESB] [2013-05-27 06:10:16,522] INFO
>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - LDAP
>> connection created successfully in read-write mode
>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}
>> TID: [0] [ESB] [2013-05-27 06:10:16,561] INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Connected
>> to mount at config in 3ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>> TID: [0] [ESB] [2013-05-27 06:10:16,690] INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Connected
>> to mount at governance in 2ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>> TID: [0] [ESB] [2013-05-27 06:10:16,819] INFO
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>> 'ad...@admin.com@proximit_esb_1 [142]' logged in at [2013-05-27
>> 06:10:16,818-0700]
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>> TID: [0] [ESB] [2013-05-27 06:12:17,207] DEBUG
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>> - Initializing the deployment synchronizer for tenant: 142
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSyncAxis2ConfigurationContextObserver}
>> TID: [0] [ESB] [2013-05-27 06:12:17,456] INFO
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>> Doing initial sync up...
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
>> TID: [0] [ESB] [2013-05-27 06:12:17,456] INFO
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>> Checking out...
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer}
>> TID: [0] [ESB] [2013-05-27 06:12:17,456] DEBUG
>> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
>> Started checkout to /mnt/
>> 10.98.175.203/wso2esb-4.6.0/repository/tenants/142 {org.w
>>
>>
>> The time gap between the highlighted parts is more than two minutes.
>>
>> 2. After that first attempt (which was unsuccessful due to timeout) the
>> second attempt for the same tenant logs into the
>> system successfully without any delays. Deployment synchronization was also
>> happened correctly.
>>
>> Any idea why this error happened in the first attempt?
>>
>> Thanks
>> --
>> Shamika Ariyawansa
>> Senior Software Engineer
>>
>> Mob:+ 94 772929486
>>
>
>
>
> --
> Dimuthu Leelarathne
> Architect & Chair of Solution Management Committee
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
