Hi Lasantha
.
Adding to my previous email, The logs show the below message [1]. In this
instance the reason for the slowness could be the RAM size
[1]TID: [0] [CEP] [2014-04-15 20:32:58,935] WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} - RAM
size (MB): 2039 of the system is below the recommended minimum size :2048
Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300
On Tue, Apr 15, 2014 at 9:14 PM, Shavantha Weerasinghe
<[email protected]>wrote:
> Hi Lasantha
>
> Sorry about the late reply, I checked the same on my home laptop and felt
> that the slowness after patch detection is notable compared to when running
> on my office lap. Yes as you said the spec of the machine has to play apart
> but good if we can check this again.
>
> Regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
>
> On Fri, Apr 11, 2014 at 2:32 PM, Lasantha Fernando <[email protected]>wrote:
>
>> Hi Shavantha,
>>
>> Are the specs for which the machine which you are running on Windows and
>> Ubuntu similar or comparable? If it is a VM, we might have to make take
>> that into consideration as well.
>>
>> Thanks,
>> Lasantha
>>
>>
>> On 11 April 2014 14:26, Shavantha Weerasinghe <[email protected]> wrote:
>>
>>> Hi All
>>>
>>> Noticed a difference in the startup time when a fresh pack starts in
>>> ubuntu and windows(run console). On windows their is a notable pause after
>>> the lines where patch changes are detected is shown.
>>>
>>> Is this normal when starting on windows
>>>
>>> Ubuntu
>>> ----------
>>> on ubuntu
>>> ----------
>>> [2014-04-11 14:05:49,236] INFO - {JMXServerManager} JMX Service URL :
>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>> [2014-04-11 14:05:49,236] INFO - {StartupFinalizerServiceComponent}
>>> Server : WSO2 Complex Event Processor-3.1.0
>>> [2014-04-11 14:05:49,237] INFO - {StartupFinalizerServiceComponent}
>>> WSO2 Carbon started in 49 sec
>>>
>>>
>>>
>>> Windows run console
>>> -----------------------------
>>> TID: [0] [CEP] [2014-04-11 14:09:49,023] INFO
>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP
>>> port : 9763
>>> TID: [0] [CEP] [2014-04-11 14:09:49,132] INFO
>>> {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
>>> - Successfully Initialized Eventing on Registry
>>> TID: [0] [CEP] [2014-04-11 14:09:49,195] INFO
>>> {org.wso2.carbon.core.init.JMXServerManager} - JMX Service URL :
>>> service:jmx:rmi://localhost:11111/jndi/rmi://localhost:9999/jmxrmi
>>> TID: [0] [CEP] [2014-04-11 14:09:49,195] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} -
>>> Server : WSO2 Complex Event Processor-3.1.0
>>> TID: [0] [CEP] [2014-04-11 14:09:49,195] INFO
>>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>>> Carbon started in 116 sec
>>>
>>>
>>> Regards,
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>
>>
>> --
>> *Lasantha Fernando*
>> Software Engineer - Data Technologies Team
>> WSO2 Inc. http://wso2.com
>>
>> email: [email protected]
>> mobile: (+94) 71 5247551
>>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
