Hi Hiranya, In my local setup this happens on the first startup. I still haven't built Senaka's commit.
thanks, dimuthu On Thu, Mar 29, 2012 at 10:22 AM, Hiranya Jayathilaka <[email protected]>wrote: > > > On Thu, Mar 29, 2012 at 10:17 AM, Charith Wickramarachchi < > [email protected]> wrote: > >> ESB Build was successful. > > > That's great. > > But I'm not fully convinced that this issue is fixed. The error occurred > before we had Emma integration stuff. And it only occurred for 2 test > modules (out of about 11). Looks more like a random error to me. > > Thanks, > Hiranya > > >> >> --Charith >> >> >> On Thu, Mar 29, 2012 at 10:05 AM, Charith Wickramarachchi < >> [email protected]> wrote: >> >>> In this case Build was triggered with r124320. According to Dimuthu the >>> fix for dropins was done at r124321. So Lets wait for the new build. >>> Now its at ESB level. >>> >>> thanks, >>> Charith >>> >>> >>> On Thu, Mar 29, 2012 at 10:00 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>>> We see that ESB startup is getting hung time to time during integration >>>> tests. This has happened twice in the last build triggered by Bamboo. In >>>> both cases the startup log is similar to the following: >>>> >>>> build 28-Mar-2012 12:59:56 [2012-03-28 12:59:56,104] INFO >>>> {org.wso2.carbon.integration.framework.utils.TestUtil} - Copying >>>> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products/esb/modules/integration/nhttp-transport/../../../../integration/security-verifier/target/SecVerifier.aar >>>> => >>>> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products/esb/modules/integration/nhttp-transport/target/carbontmp1332964791763/wso2esb-4.0.0-SNAPSHOT/repository/deployment/server/axis2services/SecVerifier.aar >>>> build 28-Mar-2012 12:59:56 [2012-03-28 12:59:56,161] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> JAVA_HOME environment variable is set to /home/bamboo/jdk1.6.0_24 >>>> build 28-Mar-2012 12:59:56 [2012-03-28 12:59:56,161] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> CARBON_HOME environment variable is set to >>>> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products/esb/modules/integration/nhttp-transport/target/carbontmp1332964791763/wso2esb-4.0.0-SNAPSHOT >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,709] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,709] INFO - CarbonCoreActivator Starting WSO2 >>>> Carbon... >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,955] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,955] INFO - CarbonCoreActivator Operating System : >>>> Linux 2.6.32-5-amd64, amd64 >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,955] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,955] INFO - CarbonCoreActivator Java Home : >>>> /home/bamboo/jdk1.6.0_24/jre >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,955] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,955] INFO - CarbonCoreActivator Java Version : >>>> 1.6.0_24 >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,956] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,955] INFO - CarbonCoreActivator Java VM : >>>> Java HotSpot(TM) 64-Bit Server VM 19.1-b02,Sun Microsystems Inc. >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,956] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,956] INFO - CarbonCoreActivator Carbon Home : >>>> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products/esb/modules/integration/nhttp-transport/target/carbontmp1332964791763/wso2esb-4.0.0-SNAPSHOT >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,956] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,956] INFO - CarbonCoreActivator Java Temp Dir : >>>> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-PRODUCTS-JOB1/products/esb/modules/integration/nhttp-transport/target/carbontmp1332964791763/wso2esb-4.0.0-SNAPSHOT/tmp >>>> build 28-Mar-2012 13:00:02 [2012-03-28 13:00:02,956] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:02,956] INFO - CarbonCoreActivator User : >>>> bamboo, en-US, America/Los_Angeles >>>> build 28-Mar-2012 13:00:03 [2012-03-28 13:00:03,254] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:03,253] INFO - RuleEngineConfigDS Successfully >>>> registered the Rule Config service >>>> build 28-Mar-2012 13:00:03 [2012-03-28 13:00:03,426] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:03,426] INFO - Activator registering the JNDI stream >>>> handler >>>> build 28-Mar-2012 13:00:03 [2012-03-28 13:00:03,612] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:03,595] INFO - ExtendedStandardService starting >>>> extended standard service : StandardService[Catalina] >>>> build 28-Mar-2012 13:00:04 [2012-03-28 13:00:04,801] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:04,801] INFO - PermissionTree Newly loaded permission >>>> tree from database for tenant 0 >>>> build 28-Mar-2012 13:00:05 [2012-03-28 13:00:05,229] INFO >>>> {org.wso2.carbon.integration.framework.utils.InputStreamHandler} - >>>> [2012-03-28 13:00:05,229] INFO - RegistryCoreServiceComponent Registry >>>> Mode : READ-WRITE >>>> build 28-Mar-2012 13:01:51 FAILED CONFIGURATION: @BeforeSuite >>>> startServer >>>> build 28-Mar-2012 13:01:51 >>>> org.testng.internal.thread.ThreadTimeoutException: Method >>>> org.testng.internal.ConfigurationMethod.startServer() didn't finish within >>>> the time-out 120000 >>>> build 28-Mar-2012 13:01:51 at >>>> java.lang.Thread.sleep(Native Method) >>>> build 28-Mar-2012 13:01:51 at >>>> org.wso2.carbon.integration.framework.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:92) >>>> build 28-Mar-2012 13:01:51 at >>>> org.wso2.carbon.integration.framework.utils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:93) >>>> build 28-Mar-2012 13:01:51 at >>>> org.wso2.carbon.integration.framework.TestServerManager.startServer(TestServerManager.java:79) >>>> build 28-Mar-2012 13:01:51 at >>>> org.wso2.esb.integration.ESBTestServerManager.startServer(ESBTestServerManager.java:24) >>>> build 28-Mar-2012 13:01:51 at >>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> build 28-Mar-2012 13:01:51 at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>> build 28-Mar-2012 13:01:51 at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>> build 28-Mar-2012 13:01:51 at >>>> java.lang.reflect.Method.invoke(Method.java:597) >>>> build 28-Mar-2012 13:01:51 at >>>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) >>>> build 28-Mar-2012 13:01:51 at >>>> org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46) >>>> build 28-Mar-2012 13:01:51 at >>>> org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) >>>> build 28-Mar-2012 13:01:51 at >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) >>>> build 28-Mar-2012 13:01:51 at >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >>>> build 28-Mar-2012 13:01:51 at >>>> java.util.concurrent.FutureTask.run(FutureTask.java:138) >>>> build 28-Mar-2012 13:01:51 at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>> build 28-Mar-2012 13:01:51 at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>> build 28-Mar-2012 13:01:51 at >>>> java.lang.Thread.run(Thread.java:662) >>>> >>>> >>>> It seems to hang right after the RegistryCoreServiceComponent has >>>> initialized. Any idea why this is happening? Please note that we haven't >>>> committed the Emma integration work yet. Also we haven't seen this in our >>>> local setups (not yet at least). >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Associate Technical Lead; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Charith Dhanushka Wickramarachchi >>> Software Engineer >>> WSO2 Inc >>> http://wso2.com/ >>> http://wso2.org/ >>> >>> blog >>> http://charithwiki.blogspot.com/ >>> >>> twitter >>> http://twitter.com/charithwiki >>> >>> Mobile : 0776706568 >>> >>> >>> >> >> >> -- >> Charith Dhanushka Wickramarachchi >> Software Engineer >> WSO2 Inc >> http://wso2.com/ >> http://wso2.org/ >> >> blog >> http://charithwiki.blogspot.com/ >> >> twitter >> http://twitter.com/charithwiki >> >> Mobile : 0776706568 >> >> >> > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dimuthu Leelarathne Technical Lead WSO2, Inc. (http://wso2.com) email: [email protected] Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
