I/O exception (java.net.SocketException) caught when processing request: Software caused connection

[Hamid Assous]

Hi,

I get the following error message in eclpise console when I execute my junit/java test on Windows 7:

INFO: I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: recv failed

org.openqa.selenium.UnhandledAlertException: Modal dialog present
Build info: version: '2.32.0', revision: '6c40c18', time: '2013-04-09 17:23:22'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_43'
Session ID: 288a14de-4b40-4950-8984-79b7aa8ac7e5
Driver info: org.openqa.selenium.ie.InternetExplorerDriver

2.33.0.0
Listening on port 15430
Jun 13, 2013 11:58:45 AM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: recv failed
Jun 13, 2013 11:58:45 AM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request

Dialog box name :This is Command line server for the IE driver:
Files that help describe the problem:
  C:\Users\qa\AppData\Local\Temp\WERCBEA.tmp.WERInternalMetadata.xml
  C:\Users\qa\AppData\Local\Temp\WERE13F.tmp.appcompat.txt
  C:\Users\qa\AppData\Local\Temp\WERE150.tmp.mdmp

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

BTW: FF is OK.

Thank you,

Hamid Assous

[Neha Shah]

Hi Hamid,

This is an intermittent INFO when HTTP server has not yet started and remote driver cannot find it.  Generally this resolves when things are up and running.  However, you may get stuck in this state and remote driver fails to launch the browser altogether.  If the later is the case, it is likely that there are IEDriever.exe processes hanging on your client.  Kill those process manually from task manager and restart your hub and node processes to rid of the error state.

Best,

Neha