On Tue, Oct 16, 2012 at 12:32 AM, Krishantha Samaraweera < [email protected]> wrote:
> AFAIK, this is bug in our products, even though we call graceful shutdown > the server process doesn't get terminated properly. http://stackoverflow.com/questions/4557144/forgetting-to-close-a-serversocket Also, it is the way sockets behave. You cannot create and close them at your will, as there are kernel implications. > Because of this issue, we had to use the forceful shutdown in new > integration framework. I have tried several times to identify the steps > to reproduce the issue but this seems to be intermittent issue. IIRC, > Charith wrote ant task or jave code to find and kill all remaining Carbon > server instance in Bamboo machine before starting integration tests. So > this issue was there from early ages. > > We will change the server shutdown logic accordingly. But we better fix > the real cause of this failure in future. I will create a JIRA for this. > > Thanks, > Krishantha. > > On Mon, Oct 15, 2012 at 11:48 AM, Samisa Abeysinghe <[email protected]>wrote: > >> We have to implement a logic where >> 1. Server shutdown logic checks if the server really went down >> 2. Force kill the server if it was not down >> 3. Server start logic checks if the server is already up >> 4. Force kill server if it is already running before starting a new one >> >> >> On Mon, Oct 15, 2012 at 11:38 AM, Nuwan Wimalasekara <[email protected]>wrote: >> >>> This is because Carbon server did not start properly after some time. >>> once one of server failed to shutdown properly while testing due to some >>> reason that will hangs server, it does not kill the server process , after >>> that other product test can not be executed. because the server start up >>> failed since all servers are starting on default port. need to figure out >>> why server is hanging while testing. will work on that >>> >>> Thanks, >>> Nuwanw >>> >>> On Sat, Oct 13, 2012 at 8:49 PM, Amila Maha Arachchi <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> There seems to besomething wrong with the PA builder. Experienced a >>>> kernel integration test failure just now. Following is the report. This >>>> only happens with the builder it seems. Not only this, I have seen the ESB >>>> integration tests hanging in the builder. What can be the reason for this? >>>> >>>> >>>> ------------------------------------------------------------------------------- >>>> Test set: TestSuite >>>> >>>> ------------------------------------------------------------------------------- >>>> Tests run: 29, Failures: 1, Errors: 0, Skipped: 28, Time elapsed: >>>> 121.205 sec <<< FAILURE! >>>> startServer(org.wso2.carbon.integration.tests.CarbonTestServerManager) >>>> Time elapsed: 120.221 sec <<< FAILURE! >>>> org.testng.internal.thread.ThreadExecutionException: >>>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: >>>> java.lang.RuntimeException: Could not login to Carbon server within 60000m >>>> s. portOffset=0 >>>> at >>>> org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25) >>>> at >>>> org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242) >>>> at >>>> org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200) >>>> at >>>> org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528) >>>> at >>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) >>>> at >>>> org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) >>>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) >>>> at org.testng.SuiteRunner.run(SuiteRunner.java:240) >>>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) >>>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) >>>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) >>>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) >>>> at org.testng.TestNG.run(TestNG.java:999) >>>> at >>>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:76) >>>> at >>>> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:161) >>>> at >>>> org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:101) >>>> at >>>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:115) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>> at >>>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) >>>> at >>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) >>>> at >>>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) >>>> at >>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) >>>> at >>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) >>>> Caused by: >>>> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: >>>> java.lang.RuntimeException: Could not login to Carbon server within >>>> 60000ms. portOffset=0 >>>> at >>>> org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:49) >>>> at >>>> org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) >>>> at >>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) >>>> at >>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>> at java.lang.Thread.run(Thread.java:662) >>>> >>>> Regards, >>>> AmilaM. >>>> -- >>>> *Amila Maharachchi* >>>> Technical Lead >>>> Member, Management Committee - Cloud & Platform TG >>>> WSO2, Inc.; http://wso2.com >>>> >>>> Blog: http://maharachchi.blogspot.com >>>> Mobile: +94719371446 >>>> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Nuwan Wimalasekara >>> Software Engineer - Test Automation >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> phone: +94 71 668 4620 >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
