dev@glassfish.java.net

Re: quicklook tests failing because of connection refused errors

From: Tim Quinn <Timothy.Quinn_at_Sun.COM>
Date: Mon, 08 Sep 2008 16:48:46 -0500

It seems like a good idea to run at least one set of Hudson tests on a
multi-core system to make it more likely we catch issues like this when
they are first introduced.

Or is that happening already and somehow this failure has just never
happened during those automated test runs?

- Tim

Carla Mott wrote:
> I'm on a dual core machine too...
>
>
> Lloyd Chambers wrote:
>> A race condition makes sense. I see 1 to 5 failure each run (variable).
>>
>> Yes, this is on a dual-core machine.
>>
>> Lloyd
>>
>>
>>
>> On Sep 8, 2008, at 2:33 PM, Jeanfrancois Arcand wrote:
>>
>>> Salut,
>>>
>>> Jerome Dochez wrote:
>>>> most likely the deployment of that application did not go through.
>>>> do you see an exception in the server log ?
>>>> Ming, could you modify the QL so it stops when deployment of one of
>>>> the tests fail. there is really no point in continuing the test run
>>>> in such a case.
>>>
>>> I do think there is a dynamic reconfiguration that happens and the
>>> listener is not ready (meaning binded on tcp port) when the
>>> exception happens. You would have received a 404 if deployment has
>>> fail. There is a thread race somewhere as I can't reproduce the
>>> issue on Ubuntu, but as soon as I use a machine that has more than
>>> one core I can see the problem. Just file a bug an assign it to me
>>> as I will do the initial investigation.
>>>
>>> Thanks
>>>
>>> -- Jeanfrancois
>>>
>>>
>>>> jerome
>>>> Carla Mott wrote:
>>>>>
>>>>> Under what conditions would I get a Connection refused error
>>>>> below? It seems it is random. The web_jspservlet_war tests were
>>>>> failing some times all and sometimes 2. When I updated my
>>>>> quicklook workspace I see that the classloader_jsf test is failing
>>>>> with the same exception and all the web_jspservlet_war tests are
>>>>> now passing. There were no changes to the web_jspservlet_war
>>>>> tests with the update.
>>>>>
>>>>> Nothing in the server.log files indicates that there is a problem.
>>>>>
>>>>> Anyone have any ideas what is going on?
>>>>>
>>>>> Thanks,
>>>>> Carla
>>>>>
>>>>>
>>>>> java.lang.Exception: java.net.ConnectException: Connection refused
>>>>> at
>>>>> test.classloader.hellojsf.helloJSFTestNG.jsfAppDeployedFirstPagetest(helloJSFTestNG.java:122)
>>>>>
>>>>> 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:585)
>>>>> at
>>>>> org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604)
>>>>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:470)
>>>>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564)
>>>>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830)
>>>>> at
>>>>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>>>>>
>>>>> at
>>>>> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>>>>> at org.testng.TestRunner.runWorkers(TestRunner.java:678)
>>>>> at org.testng.TestRunner.privateRun(TestRunner.java:624)
>>>>> at org.testng.TestRunner.run(TestRunner.java:495)
>>>>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:300)
>>>>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295)
>>>>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275)
>>>>> at org.testng.SuiteRunner.run(SuiteRunner.java:190)
>>>>> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792)
>>>>> at org.testng.TestNG.runSuitesLocally(TestNG.java:765)
>>>>> at org.testng.TestNG.run(TestNG.java:699)
>>>>> at org.testng.TestNG.privateMain(TestNG.java:824)
>>>>> at org.testng.TestNG.main(TestNG.java:802)
>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>>>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>>>>> at
>>>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>>>>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>>>>> at java.net.Socket.connect(Socket.java:520)
>>>>> at java.net.Socket.connect(Socket.java:470)
>>>>> at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
>>>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:387)
>>>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:522)
>>>>> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:639)
>>>>> at
>>>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:957)
>>>>>
>>>>> at
>>>>> java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
>>>>>
>>>>> at
>>>>> test.classloader.hellojsf.helloJSFTestNG.jsfAppDeployedFirstPagetest(helloJSFTestNG.java:97)
>>>>>
>>>>> ... 22 more
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>