3 hour timeout before getting UnreachableBrowserException

[lukeis]

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]

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]

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

• Labels added: Component-WebDriver

[lukeis]

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]

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]

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]

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]

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