9 Replies Latest reply: Jun 4, 2012 10:56 PM by krishnamrajgoud RSS

    FU Ant task failure: java.util.concurrent.ExecutionException: could not close client/server socket

    trevorbutler Community Member

      We sometimes see this failure intermitently when using the FlexUnit Ant task to run tests in a CI environment. The Ant task throws this exception:

       

      java.util.concurrent.ExecutionException: could not close client/server socket

       

      I have seen this for a while now, and still see it with the latest 4.1 RC versions.

      Here is the console output seen along with the above exception:

       

      FlexUnit player target: flash
      Validating task attributes ...
      Generating default values ...
      Using default working dir [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\Source\Flex]
      Using the following settings for the test run:
      FLEX_HOME: [C:\dev\vert-d3flxcmn32\302100.41.0.20110323122739_d3flxcmn32]
      haltonfailure: [false]
      headless: [false]
      display: [99]
      localTrusted: [true]
      player: [flash]
      port: [1024]
      swf: [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build\commons.formatter.tests.unit.sw f]
      timeout: [1800000ms]
      toDir: [C:\DJTE\commons.formatter_swc\d3flxcmn32\reports\xml]
      Setting up server process ...
      Entry  [C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build] already  available in local trust file at  [C:\Users\user\AppData\Roaming\Macromedia\Flash  Player\#Security\FlashPlayerTrust\flexUnit.cfg].
      Executing 'rundll32' with arguments:
      'url.dll,FileProtocolHandler'
      'C:\DJTE\commons.formatter_swc\d3flxcmn32\extracted\build\commons.formatter.tests.unit.swf '
      The ' characters around the executable and arguments are
      not part of the command.
      Starting server ...
      Opening server socket on port [1024].
      Waiting for client connection ...
      Client connected.
      Setting inbound buffer size to [262144] bytes.
      Receiving data ...
      Sending acknowledgement to player to start sending test data ...

      Stopping server ...
      End of test data reached, sending acknowledgement to player ...

       

       

      When the problem occurs, it is not always during the running of any particular test (that I am aware of). Recent runs where this failure was seen had the following number of tests executed (note: the total number that should be run is 45677): 18021, 18, 229.

       

      Here is a "good" run when the problem does not occur:

       

      :

      Setting inbound buffer size to [262144] bytes.
      Receiving data ...
      Sending acknowledgement to player to start sending test data ...

      Stopping server ...
      End of test data reached, sending acknowledgement to player ...
      Closing client connection ...
      Closing server on port [1024] ...
      Analyzing reports ...

      Suite: com.formatters.help.TestGeographicSiteUrls
      Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec

      :

      Suite: com.formatters.functionalUnitTest.testCases.TestNumericUDF
      Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec

      Results :

      Tests run: 45,677, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 201.186 sec

       

       

      Has anyone else ran across this problem?

       

      Thanks,

      Trevor