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
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
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
