[Carbon-dev] Event broker is registered after the message "WSO2 Carbon started in ...." when starting DSS in trunk build
Hi
There is a issue in server start up sequence. even if message is log
"WSO2 Carbon started in 38 sec". HTTPS port is not listening until event
broker is registered. that scenario found with carbon trunk build.
it takes 3 to 6 seconds to up HTTPS port after message "WSO2 Carbon started
in 38 sec".
Environment : wso2dataservices-2.6.0-SNAPSHOT
Refer : https://wso2.org/jira/browse/CARBON-12227
Server log:
[2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
Quartz scheduler 'DefaultQuartzScheduler' initialized from default
resource file in Quartz package: 'quartz.properties'
[2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
Quartz scheduler version: 2.1.1
[2012-01-17 11:09:36,423] INFO {org.quartz.core.QuartzScheduler} -
Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
[2012-01-17 11:09:36,641] INFO
{org.wso2.carbon.ntask.core.internal.TasksDSComponent} - Task service
started
[2012-01-17 11:09:36,892] INFO
{org.wso2.carbon.core.init.CarbonServerManager} -
ConfigurationContextService registered in 591ms
[2012-01-17 11:09:36,905] INFO
{org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
: 9446
[2012-01-17 11:09:36,905] INFO
{org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
: 9766
[2012-01-17 11:09:37,124] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Started
Transport Listener Manager
[2012-01-17 11:09:37,124] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
: WSO2 Data Services Server-2.6.0-SNAPSHOT
[2012-01-17 11:09:37,125] INFO
{org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
Carbon started in 34 sec
[Broker] BRK-1006 : Using configuration :
/home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
[2012-01-17 11:09:39,555] INFO {qpid.message.broker.listening} - [Broker]
BRK-1002 : Starting : Listening on TCP port 5675
[2012-01-17 11:09:39,558] INFO {qpid.message.broker.listening} - [Broker]
BRK-1002 : Starting : Listening on TCP/SSL port 8675
[2012-01-17 11:09:39,559] INFO
{org.wso2.carbon.qpid.internal.QpidServiceComponent} - Successfully
connected to the server on port 5675
[2012-01-17 11:09:39,784] INFO
{org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
- Successfully Initialized Eventing on Registry
[2012-01-17 11:09:39,801] INFO
{org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
Successfully registered the event broker
[2012-01-17 11:09:40,056] INFO
{org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
: https://10.100.3.39:9446/carbon/
Thanks
NuwanW
--
Nuwan Wimalasekara
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event broker is registered after the message "WSO2 Carbon started in ...." when starting DSS in trunk build
Hi,
This is specific to DSS, I don't see the same behavior with other products.
Some DSS automation test fail because of this inconsistent start-up order.
We can add a delay to automation tests and over come the failures. But it
is better to check why we see this only with DSS trunk build.
Can someone from DSS team please help..
Thanks,
Krishantha.
On Tue, Jan 17, 2012 at 6:44 PM, Nuwan Wimalasekara wrote:
> Hi
> There is a issue in server start up sequence. even if message is log
> "WSO2 Carbon started in 38 sec". HTTPS port is not listening until event
> broker is registered. that scenario found with carbon trunk build.
> it takes 3 to 6 seconds to up HTTPS port after message "WSO2 Carbon
> started in 38 sec".
>
> Environment : wso2dataservices-2.6.0-SNAPSHOT
>
> Refer : https://wso2.org/jira/browse/CARBON-12227
>
>
> Server log:
>
> [2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
> Quartz scheduler 'DefaultQuartzScheduler' initialized from default
> resource file in Quartz package: 'quartz.properties'
> [2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
> Quartz scheduler version: 2.1.1
> [2012-01-17 11:09:36,423] INFO {org.quartz.core.QuartzScheduler} -
> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> [2012-01-17 11:09:36,641] INFO
> {org.wso2.carbon.ntask.core.internal.TasksDSComponent} - Task service
> started
> [2012-01-17 11:09:36,892] INFO
> {org.wso2.carbon.core.init.CarbonServerManager} -
> ConfigurationContextService registered in 591ms
> [2012-01-17 11:09:36,905] INFO
> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
> : 9446
> [2012-01-17 11:09:36,905] INFO
> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
> : 9766
> [2012-01-17 11:09:37,124] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Started
> Transport Listener Manager
> [2012-01-17 11:09:37,124] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
> : WSO2 Data Services Server-2.6.0-SNAPSHOT
> [2012-01-17 11:09:37,125] INFO
> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
> Carbon started in 34 sec
> [Broker] BRK-1006 : Using configuration :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
> [2012-01-17 11:09:39,555] INFO {qpid.message.broker.listening} -
> [Broker] BRK-1002 : Starting : Listening on TCP port 5675
> [2012-01-17 11:09:39,558] INFO {qpid.message.broker.listening} -
> [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8675
> [2012-01-17 11:09:39,559] INFO
> {org.wso2.carbon.qpid.internal.QpidServiceComponent} - Successfully
> connected to the server on port 5675
> [2012-01-17 11:09:39,784] INFO
> {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
> - Successfully Initialized Eventing on Registry
> [2012-01-17 11:09:39,801] INFO
> {org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
> Successfully registered the event broker
> [2012-01-17 11:09:40,056] INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
> : https://10.100.3.39:9446/carbon/
>
>
> Thanks
> NuwanW
>
> --
> Nuwan Wimalasekara
> Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event broker is registered after the message "WSO2 Carbon started in ...." when starting DSS in trunk build
Hi Krishantha,
On Wed, Jan 18, 2012 at 10:24 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:
> Hi,
>
> This is specific to DSS, I don't see the same behavior with other
> products. Some DSS automation test fail because of this inconsistent start-up
> order.
> We can add a delay to automation tests and over come the failures. But it
> is better to check why we see this only with DSS trunk build.
>
> Can someone from DSS team please help..
>
Yeah sure. We'll check on that.
>
> Thanks,
> Krishantha.
>
> On Tue, Jan 17, 2012 at 6:44 PM, Nuwan Wimalasekara wrote:
>
>> Hi
>> There is a issue in server start up sequence. even if message is log
>> "WSO2 Carbon started in 38 sec". HTTPS port is not listening until event
>> broker is registered. that scenario found with carbon trunk build.
>> it takes 3 to 6 seconds to up HTTPS port after message "WSO2 Carbon
>> started in 38 sec".
>>
>> Environment : wso2dataservices-2.6.0-SNAPSHOT
>>
>> Refer : https://wso2.org/jira/browse/CARBON-12227
>>
>>
>> Server log:
>>
>> [2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
>> Quartz scheduler 'DefaultQuartzScheduler' initialized from default
>> resource file in Quartz package: 'quartz.properties'
>> [2012-01-17 11:09:36,423] INFO {org.quartz.impl.StdSchedulerFactory} -
>> Quartz scheduler version: 2.1.1
>> [2012-01-17 11:09:36,423] INFO {org.quartz.core.QuartzScheduler} -
>> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
>> [2012-01-17 11:09:36,641] INFO
>> {org.wso2.carbon.ntask.core.internal.TasksDSComponent} - Task service
>> started
>> [2012-01-17 11:09:36,892] INFO
>> {org.wso2.carbon.core.init.CarbonServerManager} -
>> ConfigurationContextService registered in 591ms
>> [2012-01-17 11:09:36,905] INFO
>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port
>> : 9446
>> [2012-01-17 11:09:36,905] INFO
>> {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port
>> : 9766
>> [2012-01-17 11:09:37,124] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Started
>> Transport Listener Manager
>> [2012-01-17 11:09:37,124] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server
>> : WSO2 Data Services Server-2.6.0-SNAPSHOT
>> [2012-01-17 11:09:37,125] INFO
>> {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2
>> Carbon started in 34 sec
>> [Broker] BRK-1006 : Using configuration :
>> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/repository/conf/advanced/qpid-config.xml
>> [2012-01-17 11:09:39,555] INFO {qpid.message.broker.listening} -
>> [Broker] BRK-1002 : Starting : Listening on TCP port 5675
>> [2012-01-17 11:09:39,558] INFO {qpid.message.broker.listening} -
>> [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8675
>> [2012-01-17 11:09:39,559] INFO
>> {org.wso2.carbon.qpid.internal.QpidServiceComponent} - Successfully
>> connected to the server on port 5675
>> [2012-01-17 11:09:39,784] INFO
>> {org.wso2.carbon.registry.eventing.internal.RegistryEventingServiceComponent}
>> - Successfully Initialized Eventing on Registry
>> [2012-01-17 11:09:39,801] INFO
>> {org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
>> Successfully registered the event broker
>> [2012-01-17 11:09:40,056] INFO
>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>> : https://10.100.3.39:9446/carbon/
>>
>>
>> Thanks
>> NuwanW
>>
>> --
>> Nuwan Wimalasekara
>> Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
--
Prabath Abeysekara
Software Engineer
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
