Thanks!
This can be reproduced even in a standalone pack after pointing to a MySQL.
As we understood this happens due to the deployment-time taken by samples
within ES pack.
Note the delay between two simple test we carried out with all samples and
with one sample asset.
*With all sample Gadgets and Sites* (1 min and 32 seconds)
[2015-08-07 15:50:10,909] INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Configured
Registry in 1ms
[2015-08-07 15:51:42,554] INFO {rxt-permissions} - [permissions] loading
permissions for tenant -1234
*With single sample Gadget/Site* (7 seconds)
[2015-08-07 15:22:58,595] INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Configured
Registry in 1ms
[2015-08-07 15:23:05,762] INFO {rxt-permissions} - [permissions] loading
permissions for tenant -1234
We will try to improve sample deployment process(reducing samples etc..) to
minimize this delay.
Regards,
UdaraR
On Fri, Aug 7, 2015 at 2:49 PM, Chankami Maddumage <[email protected]>
wrote:
> Hi Udara,
>
>
> 1] It takes around 9 minutes. You can see the time stamp of the
> screen-shots I attached to the Jira. And also we pointed same Oracle DB
> (remote DB) to Greg latest pack but it didn’t take this much of time to
> start the sever.
>
> 2] It takes around 2 minutes to start the sever with the ES latest pack
> with MySQL. Please note that we tested this mention scenario with registry
> mounted .
>
> On Fri, Aug 7, 2015 at 2:15 PM, Udara Rathnayake <[email protected]> wrote:
>
>> Hi Chankami,
>>
>> As per the jira I think this happens only when we point to a Oracle
>> DB(Please confirm).
>> We have few concerns before digging into this issue.
>>
>> 1. If this delay(7-10 mins) happens only for the first time what is the
>> delay (rough value) for successive starts?
>> 2. Have we noticed similar delay when we point to a remote MySQL(or any
>> remote DB)?
>>
>> Regards,
>> UdaraR
>>
>> On Thu, Aug 6, 2015 at 5:18 PM, Chankami Maddumage <[email protected]>
>> wrote:
>>
>>> Hi ES Team,
>>>
>>> As mention in [1] it takes considerable amount of time to start the
>>> sever for the first time.
>>>
>>> We need to clarify that this issue cause due to the amount of data that
>>> is logged into the registry at the initial start up.
>>>
>>> As an example we can see that disabled asset type details are logged in
>>> to the registry where sites and gadgets are the only asset types that comes
>>> as default with ES.
>>>
>>>
>>> [1] - https://wso2.org/jira/browse/STORE-958
>>>
>>>
>>> --
>>> Best Regards ,
>>>
>>>
>>> *Chankami Maddumage*
>>> Software Engineer - QA Team
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile: +94 (0) 770 030 469 <%2B94%20%280%29%20773%20381%20250>
>>>
>>>
>>
>
>
> --
> Best Regards ,
>
>
> *Chankami Maddumage*
> Software Engineer - QA Team
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94 (0) 770 030 469 <%2B94%20%280%29%20773%20381%20250>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
