3 hour timeout before getting UnreachableBrowserException #3951

Open
lukeis opened this Issue Mar 3, 2016 · 60 comments

Comments

@lukeis
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 3951

I have an automated browser task written in java that runs around the clock, using selenium
webdriver.

Occasionally, the browser crashes or exits unexpectedly. I haven't figured out why
that is happening. I upgraded to the latest version of selenium (was running 2.14.0),
and now it's even worse because when the browser crashes, while the program is waiting
for some kind of page element (via driver.findElement method), the implicit timeout
is no longer respected, and instead, there is a 3 hour (!!) timeout before the program
gets an org.openqa.selenium.remote.UnreachableBrowserException. Is there any way I
can adjust that timeout? Ideally, if the browser crashes, I should get that UnreachableBrowserException
immediately.

Selenium version: 2.21.0
OS: Windows 2008 R2 Server
Browser: IE
Browser version: 9
JVM: 1.6.0_32, 64 bit

Thank you.

Reported by arthur.blake on 2012-05-23 14:07:17

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We have seen this exact issue as well.

Selenium version: 2.21.0
Test Invocation OS: Win Server 2008 R2 (x86) - Java 1.6.0_31 (x86)
Hub OS: Win7 SP1 (x64)
Browser: FF
Browser version: ESR (10.0.2)
JVM: 1.6.0_32, 64 bit

Reported by nathan.christie on 2012-05-23 18:54:10

Member

lukeis commented Mar 3, 2016

We have seen this exact issue as well.

Selenium version: 2.21.0
Test Invocation OS: Win Server 2008 R2 (x86) - Java 1.6.0_31 (x86)
Hub OS: Win7 SP1 (x64)
Browser: FF
Browser version: ESR (10.0.2)
JVM: 1.6.0_32, 64 bit

Reported by nathan.christie on 2012-05-23 18:54:10

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member

Reported by barancev on 2012-05-24 06:15:22

  • Labels added: Component-WebDriver
Member

lukeis commented Mar 3, 2016

Reported by barancev on 2012-05-24 06:15:22

  • Labels added: Component-WebDriver
@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
This is a very critical issue esp. as selenium is adopted more and more and is run round
he clock to test business critical applications around the clock. Similar issues raised
in the past are 3874 and 3000.

Can we triage this issue on priority and resolve? We can provide any additional information
that may be needed to triage this defect and prioritize for resolution in next release
of WebDriver.

Reported by sandeepj1000 on 2012-08-29 19:26:10

Member

lukeis commented Mar 3, 2016

This is a very critical issue esp. as selenium is adopted more and more and is run round
he clock to test business critical applications around the clock. Similar issues raised
in the past are 3874 and 3000.

Can we triage this issue on priority and resolve? We can provide any additional information
that may be needed to triage this defect and prioritize for resolution in next release
of WebDriver.

Reported by sandeepj1000 on 2012-08-29 19:26:10

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We have seen exact behaviour as well.

Selenium Version : 2.25.0
OS : Windows 7 (x86)
Browser : IE 8.0.7601.17514

Reported by princekeerthi on 2012-08-30 05:53:22

Member

lukeis commented Mar 3, 2016

We have seen exact behaviour as well.

Selenium Version : 2.25.0
OS : Windows 7 (x86)
Browser : IE 8.0.7601.17514

Reported by princekeerthi on 2012-08-30 05:53:22

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I see this too.  It only started recently.  It seems from looking at the source that
the three hours is caused by the TIMEOUT_THREE_HOURS variable located in HttpClientFactory.java.
 However, this value gets overridden if a timeout greater than 0 is specified.  Looking
at a previous commit (r16445):

"The final piece of the hub/node timeout puzzle; so_timeout
made proportional to browserTimeout on node"

I went into the each node and specified browserTimeout as 60 seconds.  However I am
still seeing the issue.

Reported by L33tCodexor on 2012-09-10 19:09:16

Member

lukeis commented Mar 3, 2016

I see this too.  It only started recently.  It seems from looking at the source that
the three hours is caused by the TIMEOUT_THREE_HOURS variable located in HttpClientFactory.java.
 However, this value gets overridden if a timeout greater than 0 is specified.  Looking
at a previous commit (r16445):

"The final piece of the hub/node timeout puzzle; so_timeout
made proportional to browserTimeout on node"

I went into the each node and specified browserTimeout as 60 seconds.  However I am
still seeing the issue.

Reported by L33tCodexor on 2012-09-10 19:09:16

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I have the same issue on two different machines using the latest version of selenium
(2.25.0). Any ideas on the solution yet?

Reported by davidurbansky on 2012-09-12 18:43:39

Member

lukeis commented Mar 3, 2016

I have the same issue on two different machines using the latest version of selenium
(2.25.0). Any ideas on the solution yet?

Reported by davidurbansky on 2012-09-12 18:43:39

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Found the same UnreachableBrowserException: When the browser dies (mine is chrome and
dies because  there's an element that he doesn't find), the browser is kept there.
Meaning that the driver doesn't close() as it should.
When executing another test, since the browser is already there, the node is considered
occupied.

I get the UnreachableBrowserException when closing the grid itself. If we could reprogram
the 3 hour timeout. That would solve most problems here. Any way to do it?

Reported by ShadowsAndFlames on 2012-10-10 12:09:42

Member

lukeis commented Mar 3, 2016

Found the same UnreachableBrowserException: When the browser dies (mine is chrome and
dies because  there's an element that he doesn't find), the browser is kept there.
Meaning that the driver doesn't close() as it should.
When executing another test, since the browser is already there, the node is considered
occupied.

I get the UnreachableBrowserException when closing the grid itself. If we could reprogram
the 3 hour timeout. That would solve most problems here. Any way to do it?

Reported by ShadowsAndFlames on 2012-10-10 12:09:42

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We have also hit this issue, and would also really like a way of limiting this timeout
to 1 hour/30 mins, aswell as finding a way to kill the browser session at this point.
As documented in comment 8, my browser sessions are kept open, causing issues down
the line where further automated tests are unable to find a suitable node with capabilities.


We are considering adding some code to each node, killing any browser sessions that
last longer than a specified time. Has anyone tried doing this?

Do we have an eta on this at all?

Reported by P.Morby on 2012-11-19 13:56:22

Member

lukeis commented Mar 3, 2016

We have also hit this issue, and would also really like a way of limiting this timeout
to 1 hour/30 mins, aswell as finding a way to kill the browser session at this point.
As documented in comment 8, my browser sessions are kept open, causing issues down
the line where further automated tests are unable to find a suitable node with capabilities.


We are considering adding some code to each node, killing any browser sessions that
last longer than a specified time. Has anyone tried doing this?

Do we have an eta on this at all?

Reported by P.Morby on 2012-11-19 13:56:22

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I had this issue a while ago, and it went away, however it seems to have come back again
in the last few days.  Ubuntu with Firefox 17 and Selenium 2.25.0.  
It's possible that this firefox update is the most recent change to my system.

Reported by martin.phillips.100 on 2012-11-23 10:13:03

Member

lukeis commented Mar 3, 2016

I had this issue a while ago, and it went away, however it seems to have come back again
in the last few days.  Ubuntu with Firefox 17 and Selenium 2.25.0.  
It's possible that this firefox update is the most recent change to my system.

Reported by martin.phillips.100 on 2012-11-23 10:13:03

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Some more info on this.  Have now tried with Selenium 2.26 and get the same problem.
 Running on Windows with Firefox 17 and running in my debugger it looks like the 'hang'
is happening in:
Thread [Forwarding clickElement on session aeeea793-071e-4922-b271-d8fbfa2107e7 to
remote] (Running)

The click has taken effect and the page is now displaying the 'new page' that the click
should have loaded, but the clickElement call doesn't seem to have returned.

Manually hitting F5 on the browser to refresh the page brings things back to life and
the test carries on.

It's certainly not every 'clickElement' that results in this hang, but some do more
than others. 
I'm clicking in sequence on 4 'tabs' on a page to get the different tabs to load. 
The 3rd has sometimes 'paused' and the 4th frequently does.

The 'tabs' have the following code behind them

    <li id="billingMainMenu" class="menuItem summary">
        <script type="text/javascript">
                /* <![CDATA[ */
                $('#billingMainMenu').click(function(){
                        window.location.href="/ui/billing/instance/120";
                    });
                /* ]]> */
                </script>

                <a href="/ui/billing/instance/120">Billing</a>
            </li>



Reported by martin.phillips.100 on 2012-11-23 12:10:06

Member

lukeis commented Mar 3, 2016

Some more info on this.  Have now tried with Selenium 2.26 and get the same problem.
 Running on Windows with Firefox 17 and running in my debugger it looks like the 'hang'
is happening in:
Thread [Forwarding clickElement on session aeeea793-071e-4922-b271-d8fbfa2107e7 to
remote] (Running)

The click has taken effect and the page is now displaying the 'new page' that the click
should have loaded, but the clickElement call doesn't seem to have returned.

Manually hitting F5 on the browser to refresh the page brings things back to life and
the test carries on.

It's certainly not every 'clickElement' that results in this hang, but some do more
than others. 
I'm clicking in sequence on 4 'tabs' on a page to get the different tabs to load. 
The 3rd has sometimes 'paused' and the 4th frequently does.

The 'tabs' have the following code behind them

    <li id="billingMainMenu" class="menuItem summary">
        <script type="text/javascript">
                /* <![CDATA[ */
                $('#billingMainMenu').click(function(){
                        window.location.href="/ui/billing/instance/120";
                    });
                /* ]]> */
                </script>

                <a href="/ui/billing/instance/120">Billing</a>
            </li>



Reported by martin.phillips.100 on 2012-11-23 12:10:06

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Downgrading Firefox to 16.2 has fixed this problem, so I guess it's an issue with Firefox.
 Does anyone know of a way to tell firefox about this possible issue?

Reported by martin.phillips.100 on 2012-11-23 12:25:02

Member

lukeis commented Mar 3, 2016

Downgrading Firefox to 16.2 has fixed this problem, so I guess it's an issue with Firefox.
 Does anyone know of a way to tell firefox about this possible issue?

Reported by martin.phillips.100 on 2012-11-23 12:25:02

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Using Selenium 2.26.0, I'm having this problem when Firefox 17.0 tries to navigate to
a URL and gets a connection refused.  Couldn't we allow a user to provide their own
HttpClientFactory instance and pass it as a dependency to HttpCommandExecutor's constructor?

Reported by hertzsprung on 2012-11-29 17:07:37

Member

lukeis commented Mar 3, 2016

Using Selenium 2.26.0, I'm having this problem when Firefox 17.0 tries to navigate to
a URL and gets a connection refused.  Couldn't we allow a user to provide their own
HttpClientFactory instance and pass it as a dependency to HttpCommandExecutor's constructor?

Reported by hertzsprung on 2012-11-29 17:07:37

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Using Selenium 2.25.0 and 2.26.0 with Firefox 17.0 both display the problem, Only Fix
was to downgrade to 16.x Firefox.

Reported by scarlo@savingstar.com on 2012-12-07 15:14:22

Member

lukeis commented Mar 3, 2016

Using Selenium 2.25.0 and 2.26.0 with Firefox 17.0 both display the problem, Only Fix
was to downgrade to 16.x Firefox.

Reported by scarlo@savingstar.com on 2012-12-07 15:14:22

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
... or selenium update to 2.27

Reported by barancev on 2012-12-07 15:48:03

Member

lukeis commented Mar 3, 2016

... or selenium update to 2.27

Reported by barancev on 2012-12-07 15:48:03

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
did you try running with java 7 instead of 6?

Reported by adidon on 2013-01-16 20:38:15

Member

lukeis commented Mar 3, 2016

did you try running with java 7 instead of 6?

Reported by adidon on 2013-01-16 20:38:15

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I also have the same issue. Tired the latest selenium version but still the same. To
the comment above, I'm using Java 6, cannot move to 7 as this is required.
Is it any way how we can update the property for grid 2 for the following code in HttpClientFactory
in the selenium source:

public HttpParams getHttpParams() {
    HttpParams params = new BasicHttpParams();
    HttpConnectionParams.setSoReuseaddr(params, true);
    HttpConnectionParams.setConnectionTimeout(params, 120 * 1000);
    HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);
    params.setIntParameter(ConnConnectionPNames.MAX_STATUS_LINE_GARBAGE, 0);
    HttpConnectionParams.setStaleCheckingEnabled(params, true);
    return params;
  }
Note: we are using RemoteWebdirver with grid 2, executing on FF

Reported by yanafird on 2013-01-16 22:53:49

Member

lukeis commented Mar 3, 2016

I also have the same issue. Tired the latest selenium version but still the same. To
the comment above, I'm using Java 6, cannot move to 7 as this is required.
Is it any way how we can update the property for grid 2 for the following code in HttpClientFactory
in the selenium source:

public HttpParams getHttpParams() {
    HttpParams params = new BasicHttpParams();
    HttpConnectionParams.setSoReuseaddr(params, true);
    HttpConnectionParams.setConnectionTimeout(params, 120 * 1000);
    HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);
    params.setIntParameter(ConnConnectionPNames.MAX_STATUS_LINE_GARBAGE, 0);
    HttpConnectionParams.setStaleCheckingEnabled(params, true);
    return params;
  }
Note: we are using RemoteWebdirver with grid 2, executing on FF

Reported by yanafird on 2013-01-16 22:53:49

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I have the same issue with tests randomly hanging in Firefox WebDriver (Firefox versions
ranging from 15 to 18, Selenium 2.25.0 to 2.29.0) but always works fine in Chrome and
IE9.
Despite having both implicit and explicit wait the test never times out but sometimes
it works correctly and passes. It happens on four different computers, OS is Windows
Vista Home Premium, Vista Business and Windows 7.

Reported by sentacatest5 on 2013-01-28 08:41:19

Member

lukeis commented Mar 3, 2016

I have the same issue with tests randomly hanging in Firefox WebDriver (Firefox versions
ranging from 15 to 18, Selenium 2.25.0 to 2.29.0) but always works fine in Chrome and
IE9.
Despite having both implicit and explicit wait the test never times out but sometimes
it works correctly and passes. It happens on four different computers, OS is Windows
Vista Home Premium, Vista Business and Windows 7.

Reported by sentacatest5 on 2013-01-28 08:41:19

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Same issue here

Reported by fred@inkwireapp.com on 2013-02-01 23:32:47

Member

lukeis commented Mar 3, 2016

Same issue here

Reported by fred@inkwireapp.com on 2013-02-01 23:32:47

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I have also noticed such issue.
Tried different combination of FF (11, 16, 17) and selenium.
Issue was raised for me in 2.26.0

Start tests on VM with autodeployment and can't see the browser. But tests are able
to recover after this issue and continue. Issue was found for several times during
one test cycle execution.

org.openqa.selenium.TimeoutException: Timed out waiting for page load.
Command duration or timeout: 1800.04 seconds
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1',
java.version: '1.6.0_35'
Session ID: ea99898d-2a78-4db4-a783-6fb9d52e8a0c
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, version=11.0, cssSelectorsEnabled=true,
databaseEnabled=true, handlesAlerts=true, nativeEvents=true, webStorageEnabled=true,
applicationCacheEnabled=true, takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:187)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:533)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:246)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
    at selenium.actionbot.ActionBot._click(ActionBot.java:57)
    at selenium.actionbot.ActionBot.clickLink(ActionBot.java:305)
    at hrb.components.elements.BaseElement.click(BaseElement.java:215)
    at hrb.components.elements.BaseElement.clickAndWait(BaseElement.java:254)
    at hrb.components.elements.BaseElement.clickAndWait(BaseElement.java:250)
    at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:21)
    at $Proxy5.clickAndWait(Unknown Source)
    at hrb.navigation.Menu.clickMessages(Menu.java:157)
    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 testprocess.runner.TestCaseVersionRunner.runTestStep(TestCaseVersionRunner.java:353)
    at testprocess.runner.TestCaseVersionRunner.testCaseVersionProcess(TestCaseVersionRunner.java:205)
    at testprocess.runner.TestCaseVersionRunner.run(TestCaseVersionRunner.java:95)
    at testprocess.ProgramRunner.main(ProgramRunner.java:38)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Timed out
waiting for page load.
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1',
java.version: '1.6.0_35'
Driver info: driver.version: unknown
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:7123)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:3234)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:3241)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:382)

Reported by nikita.prikazchikov on 2013-02-05 06:20:27

Member

lukeis commented Mar 3, 2016

I have also noticed such issue.
Tried different combination of FF (11, 16, 17) and selenium.
Issue was raised for me in 2.26.0

Start tests on VM with autodeployment and can't see the browser. But tests are able
to recover after this issue and continue. Issue was found for several times during
one test cycle execution.

org.openqa.selenium.TimeoutException: Timed out waiting for page load.
Command duration or timeout: 1800.04 seconds
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1',
java.version: '1.6.0_35'
Session ID: ea99898d-2a78-4db4-a783-6fb9d52e8a0c
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, version=11.0, cssSelectorsEnabled=true,
databaseEnabled=true, handlesAlerts=true, nativeEvents=true, webStorageEnabled=true,
applicationCacheEnabled=true, takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:187)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:533)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:246)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
    at selenium.actionbot.ActionBot._click(ActionBot.java:57)
    at selenium.actionbot.ActionBot.clickLink(ActionBot.java:305)
    at hrb.components.elements.BaseElement.click(BaseElement.java:215)
    at hrb.components.elements.BaseElement.clickAndWait(BaseElement.java:254)
    at hrb.components.elements.BaseElement.clickAndWait(BaseElement.java:250)
    at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:21)
    at $Proxy5.clickAndWait(Unknown Source)
    at hrb.navigation.Menu.clickMessages(Menu.java:157)
    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 testprocess.runner.TestCaseVersionRunner.runTestStep(TestCaseVersionRunner.java:353)
    at testprocess.runner.TestCaseVersionRunner.testCaseVersionProcess(TestCaseVersionRunner.java:205)
    at testprocess.runner.TestCaseVersionRunner.run(TestCaseVersionRunner.java:95)
    at testprocess.ProgramRunner.main(ProgramRunner.java:38)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Timed out
waiting for page load.
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1',
java.version: '1.6.0_35'
Driver info: driver.version: unknown
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:7123)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:3234)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:3241)
    at <anonymous class>.<anonymous method>(file:///C:/Users/dtkachenko/anonymous4875730119239664457webdriver-profile/extensions/fxdriver@googlecode.com/components/command_processor.js:382)

Reported by nikita.prikazchikov on 2013-02-05 06:20:27

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Same happened to me over the night:

"Fail: Error communicating with the remote browser. It may have died.
Build info: version: '2.29.0', revision: '58258c3', time: '2013-1-17 22:46:43'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0.30'
Driver info: driver.version: RemoteWebDriver"

i've attached a file of my report showing that we started an action at 00:38:00 and
it ended exactly at 03:38:01.

Reported by IronWolf19 on 2013-02-05 06:41:42


- _Attachment: [ThreeHourTimeout.jpg](https://storage.googleapis.com/google-code-attachments/selenium/issue-3951/comment-21/ThreeHourTimeout.jpg)_
Member

lukeis commented Mar 3, 2016

Same happened to me over the night:

"Fail: Error communicating with the remote browser. It may have died.
Build info: version: '2.29.0', revision: '58258c3', time: '2013-1-17 22:46:43'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0.30'
Driver info: driver.version: RemoteWebDriver"

i've attached a file of my report showing that we started an action at 00:38:00 and
it ended exactly at 03:38:01.

Reported by IronWolf19 on 2013-02-05 06:41:42


- _Attachment: [ThreeHourTimeout.jpg](https://storage.googleapis.com/google-code-attachments/selenium/issue-3951/comment-21/ThreeHourTimeout.jpg)_
@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I tried to explore this too with a test that intentionally hangs (with a huge select
box)

even if I add a @Test(timeout=5000) to my Junit test that contains the hanging get()
call, it does not return until about 110s on my Windows box (Java 6)

I have to check other platforms. But if this get call was in my setup (@Before) I am
out of luck and it does not time out for at least 50 minutes on Windows.

Reported by binod80 on 2013-04-26 14:44:15

Member

lukeis commented Mar 3, 2016

I tried to explore this too with a test that intentionally hangs (with a huge select
box)

even if I add a @Test(timeout=5000) to my Junit test that contains the hanging get()
call, it does not return until about 110s on my Windows box (Java 6)

I have to check other platforms. But if this get call was in my setup (@Before) I am
out of luck and it does not time out for at least 50 minutes on Windows.

Reported by binod80 on 2013-04-26 14:44:15

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
It was fixed at grid level at revision 0acce3ba7ebc.

Need to fix at node and client levels.

Reported by a.u.savchuk on 2013-07-23 19:15:09

  • Status changed: Accepted
  • Labels added: Component-Grid
Member

lukeis commented Mar 3, 2016

It was fixed at grid level at revision 0acce3ba7ebc.

Need to fix at node and client levels.

Reported by a.u.savchuk on 2013-07-23 19:15:09

  • Status changed: Accepted
  • Labels added: Component-Grid
@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I am experiencing a similar issue when instantiating RemoteWebDriver.  The call to the
constructor just hangs there waiting on socket input.  Is there any way to break away
from it.  Interrupting the thread doesnt seem to do much.

Thank you.

Reported by ricardo.j.lopez on 2013-08-13 22:04:05

Member

lukeis commented Mar 3, 2016

I am experiencing a similar issue when instantiating RemoteWebDriver.  The call to the
constructor just hangs there waiting on socket input.  Is there any way to break away
from it.  Interrupting the thread doesnt seem to do much.

Thank you.

Reported by ricardo.j.lopez on 2013-08-13 22:04:05

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member

Reported by a.u.savchuk on 2013-08-19 16:24:27

Member

lukeis commented Mar 3, 2016

Reported by a.u.savchuk on 2013-08-19 16:24:27

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Will it be fixed for client level soon? This issue is a real pain for our test suite...

Reported by Tatsiana_Drabovich@epam.com on 2013-08-30 15:00:10

Member

lukeis commented Mar 3, 2016

Will it be fixed for client level soon? This issue is a real pain for our test suite...

Reported by Tatsiana_Drabovich@epam.com on 2013-08-30 15:00:10

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Same issue happening here, latest bits on everything.

Reported by more.andres on 2013-10-18 13:00:26

Member

lukeis commented Mar 3, 2016

Same issue happening here, latest bits on everything.

Reported by more.andres on 2013-10-18 13:00:26

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We have encountered this issue too - Windows 7 Professional, SP1, x64,
Selenium 2.32 is used in our Java automation framework using Internet Explorer 8, no
Grid.

Reported by markus.moeslinger on 2013-11-07 14:24:18

Member

lukeis commented Mar 3, 2016

We have encountered this issue too - Windows 7 Professional, SP1, x64,
Selenium 2.32 is used in our Java automation framework using Internet Explorer 8, no
Grid.

Reported by markus.moeslinger on 2013-11-07 14:24:18

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Encountered this error for Selenium 2.39 - using Grid

Reported by jason.smiley@1stdibs.com on 2014-01-22 20:31:34

Member

lukeis commented Mar 3, 2016

Encountered this error for Selenium 2.39 - using Grid

Reported by jason.smiley@1stdibs.com on 2014-01-22 20:31:34

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Note, I am starting to wonder if the BrowserTimeout field is being read as Minutes instead
of Seconds!

(my browser time out param in hub is 60)

Reported by jason.smiley@1stdibs.com on 2014-01-22 20:33:49

Member

lukeis commented Mar 3, 2016

Note, I am starting to wonder if the BrowserTimeout field is being read as Minutes instead
of Seconds!

(my browser time out param in hub is 60)

Reported by jason.smiley@1stdibs.com on 2014-01-22 20:33:49

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
This issue has been appearing randomly during our tests, sometimes it make impossible
to continue running the whole.

Reported by vmga00 on 2014-01-27 16:44:57

Member

lukeis commented Mar 3, 2016

This issue has been appearing randomly during our tests, sometimes it make impossible
to continue running the whole.

Reported by vmga00 on 2014-01-27 16:44:57

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
This issue also happens for me.  Is there a plan to resolve it?
I am using Windows 7 with Internet Explorer 10.0.
Using Selenium 2.37.0

Reported by owenfletcher on 2014-02-11 16:55:56

Member

lukeis commented Mar 3, 2016

This issue also happens for me.  Is there a plan to resolve it?
I am using Windows 7 with Internet Explorer 10.0.
Using Selenium 2.37.0

Reported by owenfletcher on 2014-02-11 16:55:56

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I've upgraded to Selenium 2.39.0 and I am still seeing the timeout issue with IE10.

Reported by owenfletcher on 2014-02-24 08:59:39

Member

lukeis commented Mar 3, 2016

I've upgraded to Selenium 2.39.0 and I am still seeing the timeout issue with IE10.

Reported by owenfletcher on 2014-02-24 08:59:39

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I'm facing the same issue and the 3 hour timeout is very annoying. As a workaround I
wrapped our testcases with a junit timeout rule, which essentially kills the thread
after 30 minutes (http://junit-team.github.io/junit/javadoc/4.10/org/junit/rules/Timeout.html).
However this leaves an open browser instance on the remote machine...

Would be great if this timeout could be adjustable!

Reported by matschbanane on 2014-03-18 15:00:34

Member

lukeis commented Mar 3, 2016

I'm facing the same issue and the 3 hour timeout is very annoying. As a workaround I
wrapped our testcases with a junit timeout rule, which essentially kills the thread
after 30 minutes (http://junit-team.github.io/junit/javadoc/4.10/org/junit/rules/Timeout.html).
However this leaves an open browser instance on the remote machine...

Would be great if this timeout could be adjustable!

Reported by matschbanane on 2014-03-18 15:00:34

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We are experiencing same issue, we use timeout in TestNG, but it still needs to be fixed!

Reported by milan.vondra on 2014-03-20 19:42:17

Member

lukeis commented Mar 3, 2016

We are experiencing same issue, we use timeout in TestNG, but it still needs to be fixed!

Reported by milan.vondra on 2014-03-20 19:42:17

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Same issue on our side too... I can't belive that almost few years passed and no solution
on this...

Reported by EOS.Roman on 2014-04-20 12:21:38

Member

lukeis commented Mar 3, 2016

Same issue on our side too... I can't belive that almost few years passed and no solution
on this...

Reported by EOS.Roman on 2014-04-20 12:21:38

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
I also faced similiar issue with Internet Explorer. I was getting WerFault.exe popup
and the test will hang for 3 hours before timeout. This 3 hour timeout is actually
http socket timeout. 
As a workaround you can modified the selenium source code in HttpClientFactory.java,
or HttpCommandExecutor.java files. In HttpClientFactory you can change the TIMEOUT_THREE_HOURS
to what ever lesser value you prefer. Or in HttpCommandExecutor add a getter for httpClientFactory.
This getter will give you access to modify the TIMEOUT value from outside selenium
code. You can have seperate monitoring thread that will change the TIMEOUT value in
case testcase hangs.
BasicHttpParams httpParams = (BasicHttpParams) ((HttpCommandExecutor)((InternetExplorerDriver)webDriver).getCommandExecutor()).getHttpClientFactory().getHttpClient().getParams();
HttpConnectionParams.setSoTimeout(httpParams, 60000);



Reported by rohitashk04 on 2014-05-12 21:19:37

Member

lukeis commented Mar 3, 2016

I also faced similiar issue with Internet Explorer. I was getting WerFault.exe popup
and the test will hang for 3 hours before timeout. This 3 hour timeout is actually
http socket timeout. 
As a workaround you can modified the selenium source code in HttpClientFactory.java,
or HttpCommandExecutor.java files. In HttpClientFactory you can change the TIMEOUT_THREE_HOURS
to what ever lesser value you prefer. Or in HttpCommandExecutor add a getter for httpClientFactory.
This getter will give you access to modify the TIMEOUT value from outside selenium
code. You can have seperate monitoring thread that will change the TIMEOUT value in
case testcase hangs.
BasicHttpParams httpParams = (BasicHttpParams) ((HttpCommandExecutor)((InternetExplorerDriver)webDriver).getCommandExecutor()).getHttpClientFactory().getHttpClient().getParams();
HttpConnectionParams.setSoTimeout(httpParams, 60000);



Reported by rohitashk04 on 2014-05-12 21:19:37

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Yes, the class org.openqa.selenium.remote.internal.HttpClientFactory has hardcoded a
two minute timeout for establishing the connection and 3 hours for starting to receive
the response (socket timeout).  There is no way to change these connection parameters
without changing Selenium code. 

 public HttpParams getHttpParams() {
    HttpParams params = new BasicHttpParams();
    HttpConnectionParams.setSoReuseaddr(params, true);
    HttpConnectionParams.setConnectionTimeout(params, 120 * 1000);
    HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);
    params.setIntParameter(ConnConnectionPNames.MAX_STATUS_LINE_GARBAGE, 0);
    HttpConnectionParams.setStaleCheckingEnabled(params, true);
    return params;
  }

Reported by jmedina@truste.com on 2014-05-12 22:01:42

Member

lukeis commented Mar 3, 2016

Yes, the class org.openqa.selenium.remote.internal.HttpClientFactory has hardcoded a
two minute timeout for establishing the connection and 3 hours for starting to receive
the response (socket timeout).  There is no way to change these connection parameters
without changing Selenium code. 

 public HttpParams getHttpParams() {
    HttpParams params = new BasicHttpParams();
    HttpConnectionParams.setSoReuseaddr(params, true);
    HttpConnectionParams.setConnectionTimeout(params, 120 * 1000);
    HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);
    params.setIntParameter(ConnConnectionPNames.MAX_STATUS_LINE_GARBAGE, 0);
    HttpConnectionParams.setStaleCheckingEnabled(params, true);
    return params;
  }

Reported by jmedina@truste.com on 2014-05-12 22:01:42

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Just some setter for timeout would be nice.
Milan

Reported by milan.vondra on 2014-05-12 22:15:16

Member

lukeis commented Mar 3, 2016

Just some setter for timeout would be nice.
Milan

Reported by milan.vondra on 2014-05-12 22:15:16

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
This is similar to issue 4319 and issue 7286

Reported by jmedina@truste.com on 2014-05-12 22:18:42

Member

lukeis commented Mar 3, 2016

This is similar to issue 4319 and issue 7286

Reported by jmedina@truste.com on 2014-05-12 22:18:42

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Apparently issue 4319 was merged into issue 4150

Reported by jmedina@truste.com on 2014-05-12 22:20:21

Member

lukeis commented Mar 3, 2016

Apparently issue 4319 was merged into issue 4150

Reported by jmedina@truste.com on 2014-05-12 22:20:21

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Pull request ready https://github.com/SeleniumHQ/selenium/pull/227

Reported by jiri.locker on 2014-06-16 15:16:30

Member

lukeis commented Mar 3, 2016

Pull request ready https://github.com/SeleniumHQ/selenium/pull/227

Reported by jiri.locker on 2014-06-16 15:16:30

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Can someone review and accept the PR from @jiri ?

I see this 3hr timeout issue as well, further details below:

Selenium version: 2.41.0
Test invocation OS: AWS LINUX _ 3.10.40-50.136.amzn1.x86_64
Hub OS: AWS LINUX _ 3.10.40-50.136.amzn1.x86_64
Browser: FF v25
Java:
[root@ip-10-x-xx-xyz ~]# java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
Date:2nd Oct 2014
This issue happens 3 out of 10 times a day

json config file:
{ "capabilities" : [ { "browserName" : "firefox",
        "firefox_binary" : "/usr/local/bin/firefox",
        "maxInstances" : 25,
        "platform" : "LINUX",
        "seleniumProtocol" : "WebDriver",
        "version" : "25"
      },
      { 
       "browserName": "chrome",
        "version": "35",
        "platform": "LINUX", 
        "maxInstances": 25, 
        "seleniumProtocol" : "WebDriver",
       }
    ],
  "configuration" : {
      "hubHost" : "10.0.17.188",
      "hubPort" : 4444,
      "maxSession" : 25,
      "port" : 5555,
      "proxy" : "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
      "register" : true,
      "registerCycle" : 10000,
      "cleanUpCycle":10000,
      "timeout":240000,
      "browserTimeout":120
    }
}

Additional Selenium Arguments
-Xms=512M 
-Xmx=1024M

Reported by eelam.ragavan on 2014-10-02 12:00:04

Member

lukeis commented Mar 3, 2016

Can someone review and accept the PR from @jiri ?

I see this 3hr timeout issue as well, further details below:

Selenium version: 2.41.0
Test invocation OS: AWS LINUX _ 3.10.40-50.136.amzn1.x86_64
Hub OS: AWS LINUX _ 3.10.40-50.136.amzn1.x86_64
Browser: FF v25
Java:
[root@ip-10-x-xx-xyz ~]# java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
Date:2nd Oct 2014
This issue happens 3 out of 10 times a day

json config file:
{ "capabilities" : [ { "browserName" : "firefox",
        "firefox_binary" : "/usr/local/bin/firefox",
        "maxInstances" : 25,
        "platform" : "LINUX",
        "seleniumProtocol" : "WebDriver",
        "version" : "25"
      },
      { 
       "browserName": "chrome",
        "version": "35",
        "platform": "LINUX", 
        "maxInstances": 25, 
        "seleniumProtocol" : "WebDriver",
       }
    ],
  "configuration" : {
      "hubHost" : "10.0.17.188",
      "hubPort" : 4444,
      "maxSession" : 25,
      "port" : 5555,
      "proxy" : "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
      "register" : true,
      "registerCycle" : 10000,
      "cleanUpCycle":10000,
      "timeout":240000,
      "browserTimeout":120
    }
}

Additional Selenium Arguments
-Xms=512M 
-Xmx=1024M

Reported by eelam.ragavan on 2014-10-02 12:00:04

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
This is the error seen in the hub log

INFO: REQUEST : {platform=LINUX, javascriptEnabled=true, cssSelectorsEnabled=false,
browserName=firefox, nativeEvents=false, rotatable=false, takesScreenshot=false, version=25}
Oct 2, 2014 8:48:57 AM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: CURRENT : {seleniumProtocol=WebDriver, platform=LINUX, firefox_binary=/usr/local/bin/firefox,
browserName=firefox, maxInstances=25, jenkins.nodeName=ip-10-0-17-154, version=25}
Oct 2, 2014 8:48:57 AM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: REQUEST : {platform=LINUX, javascriptEnabled=true, cssSelectorsEnabled=false,
browserName=firefox, nativeEvents=false, rotatable=false, takesScreenshot=false, version=25}
Oct 2, 2014 8:48:57 AM org.openqa.grid.internal.TestSlot getNewSession
INFO: Trying to create a new session on test slot {seleniumProtocol=WebDriver, platform=LINUX,
firefox_binary=/usr/local/bin/firefox, browserName=firefox, maxInstances=25, jenkins.nodeName=ip-10-0-17-154,
version=25}
Oct 2, 2014 11:49:39 AM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out
Oct 2, 2014 11:56:39 AM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out
Oct 2, 2014 12:03:39 PM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out

Reported by eelam.ragavan on 2014-10-02 12:09:24

Member

lukeis commented Mar 3, 2016

This is the error seen in the hub log

INFO: REQUEST : {platform=LINUX, javascriptEnabled=true, cssSelectorsEnabled=false,
browserName=firefox, nativeEvents=false, rotatable=false, takesScreenshot=false, version=25}
Oct 2, 2014 8:48:57 AM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: CURRENT : {seleniumProtocol=WebDriver, platform=LINUX, firefox_binary=/usr/local/bin/firefox,
browserName=firefox, maxInstances=25, jenkins.nodeName=ip-10-0-17-154, version=25}
Oct 2, 2014 8:48:57 AM hudson.plugins.selenium.JenkinsCapabilityMatcher matches
INFO: REQUEST : {platform=LINUX, javascriptEnabled=true, cssSelectorsEnabled=false,
browserName=firefox, nativeEvents=false, rotatable=false, takesScreenshot=false, version=25}
Oct 2, 2014 8:48:57 AM org.openqa.grid.internal.TestSlot getNewSession
INFO: Trying to create a new session on test slot {seleniumProtocol=WebDriver, platform=LINUX,
firefox_binary=/usr/local/bin/firefox, browserName=firefox, maxInstances=25, jenkins.nodeName=ip-10-0-17-154,
version=25}
Oct 2, 2014 11:49:39 AM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out
Oct 2, 2014 11:56:39 AM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out
Oct 2, 2014 12:03:39 PM org.openqa.grid.web.servlet.handler.RequestHandler process
SEVERE: Socket timed out for session ext. key c248125d-72b2-40b6-9ba9-f41cbf6322f9,
Read timed out

Reported by eelam.ragavan on 2014-10-02 12:09:24

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Until a proper solution is accepted I have provided a working workaround for this issue:
http://matejtymes.blogspot.co.uk/2014/10/webdriver-fix-for-unreachablebrowserexc.html

Reported by MatejTymes on 2014-10-29 00:31:49

Member

lukeis commented Mar 3, 2016

Until a proper solution is accepted I have provided a working workaround for this issue:
http://matejtymes.blogspot.co.uk/2014/10/webdriver-fix-for-unreachablebrowserexc.html

Reported by MatejTymes on 2014-10-29 00:31:49

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Pull request update: there are two alternatives proposed:
https://github.com/SeleniumHQ/selenium/pull/227 through a system property, and
https://github.com/SeleniumHQ/selenium/pull/285 through settings in the HttpClientFactory
construction.

It would be great to get at least one of these merged.

Reported by derrick@lucidchart.com on 2014-11-19 20:43:52

Member

lukeis commented Mar 3, 2016

Pull request update: there are two alternatives proposed:
https://github.com/SeleniumHQ/selenium/pull/227 through a system property, and
https://github.com/SeleniumHQ/selenium/pull/285 through settings in the HttpClientFactory
construction.

It would be great to get at least one of these merged.

Reported by derrick@lucidchart.com on 2014-11-19 20:43:52

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
+1 for https://github.com/SeleniumHQ/selenium/pull/285

Reported by matthew@lucidchart.com on 2014-11-20 19:06:14

Member

lukeis commented Mar 3, 2016

+1 for https://github.com/SeleniumHQ/selenium/pull/285

Reported by matthew@lucidchart.com on 2014-11-20 19:06:14

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Issue 8186 has been merged into this issue.

Reported by barancev on 2014-12-01 21:45:37

Member

lukeis commented Mar 3, 2016

Issue 8186 has been merged into this issue.

Reported by barancev on 2014-12-01 21:45:37

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
What is the latest update on this issue. Any solutions available for this. 

Reported by sankar.mech07 on 2014-12-22 09:53:30

Member

lukeis commented Mar 3, 2016

What is the latest update on this issue. Any solutions available for this. 

Reported by sankar.mech07 on 2014-12-22 09:53:30

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Issue 8141 has been merged into this issue.

Reported by barancev on 2015-04-03 08:02:52

Member

lukeis commented Mar 3, 2016

Issue 8141 has been merged into this issue.

Reported by barancev on 2015-04-03 08:02:52

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
We do face the same issue. Our Test hangs in for 3 hours and then gets killed. Any work
around for this would be a great help.

Reported by rkhaneds on 2015-04-09 16:59:00

Member

lukeis commented Mar 3, 2016

We do face the same issue. Our Test hangs in for 3 hours and then gets killed. Any work
around for this would be a great help.

Reported by rkhaneds on 2015-04-09 16:59:00

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Facing this issue in Firefox 35 & above in selenium 44 & 45.

I'm using timeouts to handle this. Please fix asap.

Reported by manjunathscp on 2015-04-20 14:44:14

Member

lukeis commented Mar 3, 2016

Facing this issue in Firefox 35 & above in selenium 44 & 45.

I'm using timeouts to handle this. Please fix asap.

Reported by manjunathscp on 2015-04-20 14:44:14

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Occasionally reproducing issue.

Versions: Chrome 39.0.2171.71m, Firefox 33.1.1, WebDriver 2.44.0, SeleniumGrid 2.44.0

Reported by chernyak.andrew on 2015-04-20 16:46:52

Member

lukeis commented Mar 3, 2016

Occasionally reproducing issue.

Versions: Chrome 39.0.2171.71m, Firefox 33.1.1, WebDriver 2.44.0, SeleniumGrid 2.44.0

Reported by chernyak.andrew on 2015-04-20 16:46:52

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
The same problem, Webdriver 2.44.0 and Firefox 33.

Generally the problem occurs when the page is in state loading and i try to execute
a webdriver API funcion or i try to execute a sentence with JavascriptExecutor

I ned a way to modify HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);

Reported by voyadominarelmundo on 2015-04-24 08:26:12

Member

lukeis commented Mar 3, 2016

The same problem, Webdriver 2.44.0 and Firefox 33.

Generally the problem occurs when the page is in state loading and i try to execute
a webdriver API funcion or i try to execute a sentence with JavascriptExecutor

I ned a way to modify HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);

Reported by voyadominarelmundo on 2015-04-24 08:26:12

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Seeing this with FireFox 31.6 ESR and webdriver 2.44.0

Reported by thayes@amplify.com on 2015-05-13 15:15:58

Member

lukeis commented Mar 3, 2016

Seeing this with FireFox 31.6 ESR and webdriver 2.44.0

Reported by thayes@amplify.com on 2015-05-13 15:15:58

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
You can fix the issue by having the browser timeout in your HUB.  We implemented in
our global framework it works successfully. We had the same issue of which our test
was running more then 3 Hours.

Reported by DiscoveryATtest on 2015-05-21 18:38:56

Member

lukeis commented Mar 3, 2016

You can fix the issue by having the browser timeout in your HUB.  We implemented in
our global framework it works successfully. We had the same issue of which our test
was running more then 3 Hours.

Reported by DiscoveryATtest on 2015-05-21 18:38:56

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Can you be more specific on HUB configuration? You mean browserTimeout? Because I have
tried all timers and nothing seems to work, I still get the 3-hour timeout.

Reported by StouRou on 2015-07-02 08:48:15

Member

lukeis commented Mar 3, 2016

Can you be more specific on HUB configuration? You mean browserTimeout? Because I have
tried all timers and nothing seems to work, I still get the 3-hour timeout.

Reported by StouRou on 2015-07-02 08:48:15

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Agreed with the above comment. Even after configuring all timeouts (both
from script and Grid/Node) this is still happening every now and then.

Reported by manjunathscp on 2015-07-02 09:18:13

Member

lukeis commented Mar 3, 2016

Agreed with the above comment. Even after configuring all timeouts (both
from script and Grid/Node) this is still happening every now and then.

Reported by manjunathscp on 2015-07-02 09:18:13

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Same issue with docker-selenium. The timeouts don't seem to prevent the hanging.

Reported by dhruv@dhruvbhatia.com on 2015-07-30 00:20:14

Member

lukeis commented Mar 3, 2016

Same issue with docker-selenium. The timeouts don't seem to prevent the hanging.

Reported by dhruv@dhruvbhatia.com on 2015-07-30 00:20:14

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member
Hub configuration below:
**************************

Sorry for the delay for your question above this is how i have configured my HUB.

-Xmx512m -jar *Provide your Jar file here* -role hub -port 1000 –timeout 125 –browserTimeout
125

Reported by rkhaneds on 2015-08-04 16:52:49

Member

lukeis commented Mar 3, 2016

Hub configuration below:
**************************

Sorry for the delay for your question above this is how i have configured my HUB.

-Xmx512m -jar *Provide your Jar file here* -role hub -port 1000 –timeout 125 –browserTimeout
125

Reported by rkhaneds on 2015-08-04 16:52:49

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Mar 3, 2016

Member

Reported by luke.semerau on 2015-09-17 17:44:49

  • Labels added: Restrict-AddIssueComment-Commit
Member

lukeis commented Mar 3, 2016

Reported by luke.semerau on 2015-09-17 17:44:49

  • Labels added: Restrict-AddIssueComment-Commit
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.