http://code.google.com/p/selenium/source/browse/trunk/java/server/src/org/openqa/grid/internal/ActiveTestSessions.java,
I see my message here, but have no ideas who fills in reason as TIMEOUT

Oh, I reread wiki and source.
And probably I a bit confused of all information in
http://code.google.com/p/selenium/wiki/Grid2

I cannot understand where it is here:
http://code.google.com/p/selenium/source/browse/trunk/java/server/src/org/openqa/grid/common/defaults/GridParameters.properties
Property with name timeout exists here:
http://code.google.com/p/selenium/source/browse/trunk/java/server/src/org/openqa/grid/common/defaults/DefaultHub.json
But it looks it is 300 secs, what is much more than I could have.

I can only assume that some properties are hardcoded, and I need to find what is the
right place to set this timeout.

Oh, It looks there is some strange default config:
cleanUpCycle : 5000
timeout : 300000

It means browsers will be stopped each five secs, (and in tests I have similar sleeps)
however session is treated dead only after 5 mins.
And what I see is:
- tests hangs for 5 mins. and only than I notified about timeout.
What I expect is:
- timeout should be less than cleanup, because cleanup will always clean session. or
they should have absolutely different meanings (possible restriction to set one less
other)
- immediate exception on timeout, because session was already clean up, no sense to
wait for 5 mins, just to be notified that session was cleanup 295 seconds ago.

I will keep playibg with tiemouts... :)

Hello,

Have you found a solution, i have the same issue with different configurations of the
my Grid. I'm using the Grid in version 2.26.0

Thanks

Hi,
I am getting the same error browser timeout,Anyone has a solution for this ? Please
help !!! We are using Grid to run our tests.

Hi!

1. i'd recommend to store all configuration in JSON files, both hub and nodes. It simplifies
setup and configuration.

2. About time parameters:

* timeout - if after this time interval node does not responce to client command it
supposed as hanged and removed from hub node pool. So another tests will not be executed
on hanged node but on another node which capable with desired and requested capabilities.
In seconds. If it is happened then in error message string TIMEOUT is shown.

* browserTimeout - if after this interval browser does not return result of sent command
it supposed that browser hangs and test session will be killed. If it is happenede
in error message should be string as BROWSER_TIMEOUT. In seconds.

* cleanUpCycle - interval between cleaning timeout test sessions. In milliseconds.
So 5000 means that each 5 seconds special process checks is time of execution of command
on node is more that timeout, and if it so then delete node from hub pool.

* registerCycle - interval between register tries of node on hub. In milliseconds.
So 5000 means that node process will perfom register request to hub every 5 seconds.
It is useful for hub failure/crash or restarting. If hub is restarted after this 5
seconds all nodes will be registered on hub and tests can continue to execute.


Also all these params can be setted up on hub - then they will be used as default values
for all nodes which does not overwrite these, and on node - then hub values will be
ignored.
This is my understanding of these parameters. Maybe i'm wrong with this :)

Also from my point of view it is not a bug of selenium functionality
but bug of selenium documentation. 

Is this issue still actual? Is this a documentation issue?

Alexandr Savchuk—
It sounds like you're saying that this is not a bug in the hub, but it seems to me
that it is still a bug in the node. That is, the node has hung and that's a problem,
but the hub is taking the appropriate action for such a situation. Anyway, I don't
understand how this could be seen as merely a documentation issue. The node bug should
be fixed so that nodes don't hang.

Alexei Barantsev—
Yes, this is still occurring as of version 2.30.0.

Of course, if his really is a bug in the node and not in the hub, then what on Earth
does parallelization have to do with it? In my case, each node is never running more
than one test at a time.

To clarify, Alexandr, are you saying that there is a currently undocumented way to work
around this problem without giving up parallelization?

In the situation outlined here, the node has not hung.  The client has sat idle for
a period of time exceeding the timeout.  In this case, the hub assumes the client has
disconnected or errored out and thus issues a close session command to the node.  The
node complies and the hub notes that the session has closed.  The client then tries
to use the session ID again, but it's since been closed.

The solution is to either adjust the timeout setting as appropriate for your environment
or don't idle clients that already have sessions open.

The documentation matter came up because the previous comment mentioned the grid 1
timeout parameters, whereas the issue is filed against grid 2.  The grid 2 timeout
parameters are documented on the grid wiki page:

https://code.google.com/p/selenium/wiki/Grid2

Thus far, I haven't seen anything that really constitutes a bug; just a misunderstanding
of how grid operates.  If someone can point to something not working as intended or
documented, please let me know.

I have similar issue with timeouts.
hub/node version - 2.37
FireFox
Here are some extractions from logs(sorry some info is erased since NDA agreement):
12-03 00:04:54 [TestNGInvoker-setUp()] INFO com.tomtom.qa.selenium.framework.BaseTest
- Current driver: RemoteWebDriver: firefox on XP (9c2dbb4c-7f32-4ca7-9461-5dc0af0513fa)
..... some data preparation goes in this period of time
12-03 00:09:46 [TestNGInvoker-testZones()] INFO com.selenium.framework.BaseTest - 
 Exception : current URL : null
12-03 00:09:46 [pool-2-thread-6] ERROR com.selenium.helpers.ScreenshotListener - java.lang.Exception:
 The exception occured org.openqa.selenium.WebDriverException: Session [9c2dbb4c-7f32-4ca7-9461-5dc0af0513fa]
was terminated due to BROWSER_TIMEOUT
Command duration or timeout: 6 milliseconds
Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42',
time: '2013-10-18 09:51:02'
System info: host: 'nlsrvup-hud05', ip: '10.96.196.16', os.name: 'Linux', os.arch:
'amd64', os.version: '2.6.32-220.el6.x86_64', java.version: '1.6.0_27-ea'
Session ID: 9c2dbb4c-7f32-4ca7-9461-5dc0af0513fa
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, webdriver.remote.sessionid=9c2dbb4c-7f32-4ca7-9461-5dc0af0513fa,
version=25.0.1, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true,
browserConnectionEnabled=true, webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=true,
takesScreenshot=true}]
    at com.selenium.framework.BaseTest.runEmulator(BaseTest.java:538)
    at com.selenium.framework.BaseTest.startEmulator(BaseTest.java:650)
    at com.selenium.MyContentPageTests.testZones().changeTheMapZones(testZones.java:49)
    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 org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
    at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46)
    at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

The hub is started  with java -jar selenium-server-standalone-2.37.0.jar -role hub -timeout
1000 -browserTimeout 1000 -cleanUpCycle 1000000
The timeouts on nodes are not configured, so they are taking grid timeout configuration.
What i see is that timeout/browserTimeout is equal to ~16 minutes, browser is opened
in beforeClass method, data preparation takes ~5 minutes, after which test is started.
Data preparation is not sending any browser(webDriver) requests.
When browser operation is initiated, the session is already dropped and BROWSER_TIMEOUT
exception is thrown.

I believe it can be reproduced just with introducing some 6 minutes sleep inside test
method, after that perform some browser interaction, and you will see that browser
is dead.

Tried to playaround with timeout configuration, and no success. Why sessions becomes
dead in 5 minutes time frame?

Here is what hub says on web page config:
Config for the hub :
host : null
port : 4444
cleanUpCycle : 1000000
timeout : 1000000
browserTimeout : 1000000
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :

2.35 version with same configs returns TIMEOUT exception, instead of BROWSER_TIMEOUT.
I think the priority of this issue should be increased

Is there a way to avoid this? It's really hurting my automation.

Hi i'm facing the same: when running with below mentioned TestNg annotations and grid
version(2.39.0)  & Selenium Webdriver version(2.40.0)  

@Test(invocationCount = 4,threadPoolSize = 2)

//error log below

org.openqa.selenium.WebDriverException: Session [b3f8c2d9-11b9-4180-8b66-21314114f5d8]
was terminated due to CLIENT_STOPPED_SESSION
Command duration or timeout: 8 milliseconds
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:55:11'
System info: host: 'SF-CORP-TS-02', ip: '10.15.15.98', os.name: 'Windows Server 2008
R2', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_51'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{platform=XP, javascriptEnabled=true, acceptSslCerts=true, browserName=firefox,
rotatable=false, locationContextEnabled=true, webdriver.remote.sessionid=b3f8c2d9-11b9-4180-8b66-21314114f5d8,
version=27.0.1, databaseEnabled=true, cssSelectorsEnabled=true, handlesAlerts=true,
browserConnectionEnabled=true, webStorageEnabled=true, nativeEvents=false, applicationCacheEnabled=true,
takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:573)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:326)
    at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:423)
    at org.openqa.selenium.By$ByXPath.findElement(By.java:357)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318)
    at unitfiles.align.net.Driver.login(Driver.java:147)
    at unitfiles.align.net.Driver.addMatterAndModel(Driver.java:162)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
    at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
    at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
    at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
    at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Session
[b3f8c2d9-11b9-4180-8b66-21314114f5d8] was terminated due to CLIENT_STOPPED_SESSION
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:55:11'
System info: host: 'SF-CORP-TS-02', ip: '10.15.15.98', os.name: 'Windows Server 2008
R2', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_51'
Driver info: driver.version: unknown
    at org.openqa.grid.internal.ActiveTestSessions.getExistingSession(ActiveTestSessions.java:104)
    at org.openqa.grid.internal.Registry.getExistingSession(Registry.java:423)
    at org.openqa.grid.web.servlet.handler.RequestHandler.getSession(RequestHandler.java:235)
    at org.openqa.grid.web.servlet.handler.RequestHandler.process(RequestHandler.java:117)
    at org.openqa.grid.web.servlet.DriverServlet.process(DriverServlet.java:84)
    at org.openqa.grid.web.servlet.DriverServlet.doPost(DriverServlet.java:68)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.seleniumhq.jetty7.servlet.ServletHolder.handle(ServletHolder.java:565)
    at org.seleniumhq.jetty7.servlet.ServletHandler.doHandle(ServletHandler.java:479)
    at org.seleniumhq.jetty7.server.session.SessionHandler.doHandle(SessionHandler.java:225)
    at org.seleniumhq.jetty7.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
    at org.seleniumhq.jetty7.servlet.ServletHandler.doScope(ServletHandler.java:406)
    at org.seleniumhq.jetty7.server.session.SessionHandler.doScope(SessionHandler.java:186)
    at org.seleniumhq.jetty7.server.handler.ContextHandler.doScope(ContextHandler.java:965)
    at org.seleniumhq.jetty7.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
    at org.seleniumhq.jetty7.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
    at org.seleniumhq.jetty7.server.Server.handle(Server.java:349)
    at org.seleniumhq.jetty7.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
    at org.seleniumhq.jetty7.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)
    at org.seleniumhq.jetty7.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
    at org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
    at org.seleniumhq.jetty7.http.HttpParser.parseNext(HttpParser.java:857)
    at org.seleniumhq.jetty7.http.HttpParser.parseAvailable(HttpParser.java:235)
    at org.seleniumhq.jetty7.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)
    at org.seleniumhq.jetty7.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)
    at org.seleniumhq.jetty7.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
    at org.seleniumhq.jetty7.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
    ... 1 more

More info on Above issue:

exception occurred  when executing thread.sleep(1000) command, i'm new to grid i could
be doing something wrong.. let me know if this is issu with selenium server or it's
wrong to use thread.sleep

thanks
Abhi

I think that the problem here is that:

https://code.google.com/p/selenium/wiki/Grid2

says that timeout and browserTimetou are in seconds but in:

https://code.google.com/p/selenium/source/browse/java/server/src/org/openqa/grid/common/defaults/DefaultHub.json

you can see that the timeout seems to be using values in miliseconds!!

So if you use:

-timeout 1000 -browserTimeout 1000

you have set timeouts of 1 second!!

I was having the same exceptions and I confirmed in my case that this was the problem.
So I'm pretty sure that you are having the same problem.
I'm using Selenium standalone server 2.39.0 and json config files.

This happened to us too, very frustrating. Thanks for the feedback on trying milliseconds
vs seconds. That's something I never would've figured out without reading your comment.

Oct 08, 2014 12:00:24 PM com.on24.apollo.Test.TestBase setUp
INFO: setUp start
log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager).
log4j:WARN Please initialize the log4j system properly.
Oct 08, 2014 12:01:32 PM com.on24.apollo.Test.TestBase setUp
INFO: setUp complete CustomWebDriver: iPhone on MAC (6df8d206-c953-4411-94f3-02cc010317fe)
      System info: os.name: MacOS  32-bit, browser.name: iPhone, browser.version: 7.0
Oct 08, 2014 12:01:45 PM com.on24.apollo.Test.Steps.CucumberUtil embedScreenshot
WARNING: getting screenshot...
Oct 08, 2014 12:01:53 PM com.on24.apollo.Test.Steps.CucumberUtil embedScreenshot
WARNING: getting screenshot...
Oct 08, 2014 12:02:27 PM com.on24.apollo.Test.Steps.CucumberUtil embedScreenshot
WARNING: getting screenshot...
Session [6df8d206-c953-4411-94f3-02cc010317fe] was terminated due to TIMEOUT
Command duration or timeout: 10 milliseconds
Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42',
time: '2013-10-18 09:51:02'
System info: host: 'RANI-PC', ip: '10.2.20.185', os.name: 'Windows 7', os.arch: 'x86',
os.version: '6.1', java.version: '1.7.0_67'
Session ID: 6df8d206-c953-4411-94f3-02cc010317fe
Driver info: com.on24.apollo.util.CustomWebDriver
Capabilities [{platform=MAC, app=safari, javascriptEnabled=true, browserName=iPhone,
desired={platform=MAC, app=safari, browserName=iPhone, device=iPhone Simulator, deviceOrientation=landscape,
version=7.0}, locationContextEnabled=false, version=7.0, databaseEnabled=false, webStorageEnabled=false,
safari=true, device=iPhone Simulator, deviceOrientation=landscape, warnings={}, takesScreenshot=true}]
Oct 08, 2014 12:02:27 PM com.on24.apollo.Test.Steps.CucumberUtil embedScreenshot
WARNING: getting screenshot...
Session [6df8d206-c953-4411-94f3-02cc010317fe] was terminated due to TIMEOUT
Command duration or timeout: 5 milliseconds
Build info: version: '2.37.0', revision: 'a7c61cbd68657e133ae96672cf995890bad2ee42',
time: '2013-10-18 09:51:02'
System info: host: 'RANI-PC', ip: '10.2.20.185', os.name: 'Windows 7', os.arch: 'x86',
os.version: '6.1', java.version: '1.7.0_67'
Session ID: 6df8d206-c953-4411-94f3-02cc010317fe
Driver info: com.on24.apollo.util.CustomWebDriver
Capabilities [{platform=MAC, app=safari, javascriptEnabled=true, browserName=iPhone,
desired={platform=MAC, app=safari, browserName=iPhone, device=iPhone Simulator, deviceOrientation=landscape,
version=7.0}, locationContextEnabled=false, version=7.0, databaseEnabled=false, webStorageEnabled=false,
safari=true, device=iPhone Simulator, deviceOrientation=landscape, warnings={}, takesScreenshot=true}]

The above issue comes when i ran test on appium in pad simulator.

Please help me on this issue.i have use all the above suggestions.
Where timoeut<cleanup cycle and all but no one is useful for me.Please suggest a solution
to this problem.I comes after 2 scenarios pass.

I am also facing same issue: Session was terminated due to SO_TIMEOUT.
Could any one provide resolution for this?

Configurations:
browsers: Firefox 30,31,32
Selenuim: 2.43.1

Using grid and node concept

Is there anyone who is running parallel test? I am also trying to run my test in parallel
mode but its not working. Every time I am getting session timeout 

I am also getting the same issue "org.openqa.selenium.WebDriverException: Session []
was terminated due to TIMEOUT" on version 2.44.0.

This issue specific to Selenium Grid only. Browser got crashed after 5 mins.

ANy help would be appreciated.

Only started getting this recently too with Grid Console v.2.45.0