Hi, I'm having the same problem since 2.1.0. 
Tests that never failed are now failing sometimes.

Some tests fail even before they start. This is the warning from HUB:

Warning: session ext. key c24f616f4ef14fc4840b33680df13168 has been ORPHANED and will
be released.

And here ist the exception:

Session not available - [c24f616f4ef14fc4840b33680df13168 (int. key, remote not contacted
yet.)]

Selenium version: 2.1.0
OS: Windows XP
Browser: Firefox
Browser version: 5

Are you doing anything strange list creating a session and then never sending any other
commands?  The ORPHANED bit basically means the session was created but then no other
commands were routed to it.

It's strange but it seems that the session is not starting fast enough. 
When I run the tests at my local machine is everything okay. But when I start the same
tests at a remote desktop I always get these exceptions. This hapens because the session
is taking to long to be initialized. Any workarounds? Thks.

I'll have to double-check later, but I don't think the orphan check happens until after
the session has fully started.  If not, that's a bug.

I think two issues have been confused here. The original -- sessions being unavailable,
and a second -- sessions being orphaned. For those experiencing the latter please raise
a separate issue and provide as much detail as possible.

I'm not sure which issue comment 6 relates to, but I can say that the original issue
that I reported does indeed occur with Selenium RC nodes.

@Dave, I was actually referring to the original issue only. I tried multiple times to
recreate the session being unavailable issue using RC node, but couldn't. Since you
said you are able to replicate it, I can delete my previous comment

Okay, thanks for the clarification.

Did anyone face this issue in IE or googleChrome? Or is this happening only in FF?

@Dave, while starting the node, did you use the default setting for browsers? Or did
you specify -browser parameter? I am just trying to see whether this issue is specific
to any browser OR scenario. 

Hello,

I have the same issue, randomly. For info it's IE 7 only:
java -jar selenium-server-standalone.jar -role rc -port 4444 -hub http://myhub:4444/grid/register
-browser "browserName=*iexplore,version=7,maxInstances=3,platform=WINDOWS"

Regards,
Julien

@Julien: I think your issue is different. Have you tried a single server, no grid, and
multiple IE. Last time i tried i was only possible to start 1 IE per OS using the java
client.
thanks
françois

All, 
I have been running few tests continuously to see whether there is a pattern for this
failure. Here is what I have found

During the test, one of the requests will get timed out. From what I have seen, the
page doesn't load completely when this issue happens. This causes a node TIMEOUT to
happen. Hub would then send Delete Session command to the node, but that command doesn't
get any response from node. I could still see the browser open and waiting for the
page to load even after that delete session command was executed. 

I don't know the reasons for both, but thought it might help in resolving the issue.

Is there anything that I can do to get this issue fixed?

Whilst testing with 2.5 I have seen an additional message with these failures:

Error 500 org.openqa.grid.internal.GridException: cannot forward the request Timeout
waiting for connection

It would appear that this relates to line #153 in /trunk/java/server/src/org/openqa/grid/web/servlet/handler/RequestHandler.java

As a result of this timeout the session is terminated, which would explain the following
failure of session not available.

Are there more changes which are yet to be committed for this issue? I took the latest
from repository yesterday. I could still replicate the issue. Error message is same
as the previous one. 

Reopened

I'm no longer seeing this with Selenium 2.6.0. Please reopen if anyone can reproduce
with the latest version.

Hi Dave, it still doesn't work for me. Below outputs from the console for hub and client:

Server:


D:\>java -jar selenium-server-standalone-2.6.0.jar -role hub
14-Sep-2011 14:27:21 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
14-Sep-2011 14:27:21 org.openqa.jetty.http.HttpServer doStart
INFO: Version Jetty/5.1.x
14-Sep-2011 14:27:21 org.openqa.jetty.util.FileResource <clinit>
INFO: Checking Resource aliases
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.servlet.WebApplicationHandler@41d05d
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started WebApplicationContext[/,/]
14-Sep-2011 14:27:22 org.openqa.jetty.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:4444
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.Server@8a0d5d
14-Sep-2011 14:27:27 org.openqa.grid.web.servlet.handler.RequestHandler handleNewSession
WARNING: WARNING : using a beforeSession on a proxy that can support multiple tests
is risky.
14-Sep-2011 14:27:37 org.openqa.grid.internal.RemoteProxy$CleanUpThread run
WARNING: session ext. key 1316006743657 has been ORPHANED and will be released
timing out ext. key 1316006743657



Client:


D:\>java -jar selenium-server-standalone-2.6.0.jar -role hub
14-Sep-2011 14:27:21 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
14-Sep-2011 14:27:21 org.openqa.jetty.http.HttpServer doStart
INFO: Version Jetty/5.1.x
14-Sep-2011 14:27:21 org.openqa.jetty.util.FileResource <clinit>
INFO: Checking Resource aliases
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.servlet.WebApplicationHandler@41d05d
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started WebApplicationContext[/,/]
14-Sep-2011 14:27:22 org.openqa.jetty.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:4444
14-Sep-2011 14:27:22 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.Server@8a0d5d
14-Sep-2011 14:27:27 org.openqa.grid.web.servlet.handler.RequestHandler handleNewSession
WARNING: WARNING : using a beforeSession on a proxy that can support multiple tests
is risky.
14-Sep-2011 14:27:37 org.openqa.grid.internal.RemoteProxy$CleanUpThread run
WARNING: session ext. key 1316006743657 has been ORPHANED and will be released
timing out ext. key 1316006743657



The hub and client are on a different machines.

Stan, the orphaned sessions is a separate issue. I have also seen this as reported in
issue 2175, however I was unable to reproduce it with the latest version. Please provide
any further information that may help us investigate this (os name/version, browser
name/version, etc) in issue 2175.

Also, it looks like you've pasted the same output for both server and client.

I have the same issue in the server 2.6.0:
HUB: java -Xms512m -jar selenium-server-standalone-2.6.0.jar -role hub -maxSession
400
CLIENTS:
java -Xms1024m -jar selenium-server-standalone-2.6.0.jar -role webdriver -hub http://serverhost:4444/grid/register
-port 5558 -maxSession 150 -browser "browserName=htmlunit,maxInstances=150,platform=LINUX"

java -Xms1024m -jar selenium-server-standalone-2.6.0.jar -role webdriver -hub http://serverhost:4444/grid/register
-port 5555 -maxSession 150 -browser "browserName=htmlunit,maxInstances=150,platform=LINUX"

java -Xms1024m -jar selenium-server-standalone-2.6.0.jar -role webdriver -hub http://serverhost:4444/grid/register
-port 5556 -maxSession 150 -browser "browserName=htmlunit,maxInstances=150,platform=LINUX"

each client host is dedicated machine. I use TestNG and have the next exception in
results:
org.openqa.selenium.WebDriverException: Session [1316189175716] not available - [ext.
key 1316189238402, ext. key 1316189175706, ext. key 1316190075729, ext. key 1316189238404,
ext. key 1316189175707, ext. key 1316190075730, ext. key 1316189238403, ext. key 1316189175708,
ext. key 1316190075731, ext. key 1316189238405, ext. key 1316189175709, ext. key 1316190075732,
ext. key 1316189238406, ext. key 1316189175710, ext. key 1316190075733, ext. key 1316189238407,
ext. key 1316189175711, ext. key 1316190075734, ext. key 1316189238408, ext. key 1316189175712,
ext. key 1316190075736, ext. key 1316189238409, ext. key 1316189175713, ext. key 1316190075735,
ext. key 1316189238411, ext. key 1316189175714, ext. key 1316190075737, ext. key 1316189238410,
ext. key 1316189175715, ext. key 1316190075738, ext. key 1316189238412, ext. key 1316190075739,
ext. key 1316189238413, ext. key 1316189175717, ext. key 1316190075740, ext. key 1316189238414,
ext. key 1316189175718, ext. key 1316190075741, ext. key 1316189238415, ext. key 1316189175719,
ext. key 1316190075742, ext. key 1316189175720, ext. key 1316190075743, ext. key 1316189238417,
ext. key 1316190075744, ext. key 1316189238418, ext. key 1316189175722, ext. key 1316190075745,
ext. key 1316189238420, ext. key 1316189175723, ext. key 1316190075746, ext. key 1316189238419,
ext. key 1316189175724, ext. key 1316190075747, ext. key 1316189238421, ext. key 1316189175725,
ext. key 1316190075748, ext. key 1316189238422, ext. key 1316189175726, ext. key 1316190075749,
ext. key 1316189238423, ext. key 1316189175727, ext. key 1316190075750, ext. key 1316189238424,
ext. key 1316189175728, ext. key 1316190075751, ext. key 1316189238425, ext. key 1316189175729,
ext. key 1316190075752, ext. key 1316189238426, ext. key 1316189175730, ext. key 1316190075753,
ext. key 1316189238427, ext. key 1316189175731, ext. key 1316190075754, ext. key 1316189238428,
ext. key 1316189175732, ext. key 1316190075755, ext. key 1316189238429, ext. key 1316189175733,
ext. key 1316190075756, ext. key 1316189238430, ext. key 1316189175734, ext. key 1316190075757,
ext. key 1316189238431, ext. key 1316189175735, ext. key 1316190075758, ext. key 1316189238432,
ext. key 1316189175736, ext. key 1316190075759, ext. key 1316189238433, ext. key 1316189175737,
ext. key 1316190075760, ext. key 1316189238434, ext. key 1316189175738, ext. key 1316190075761,
ext. key 1316189238435, ext. key 1316189175739, ext. key 1316190075764, ext. key 1316189238443,
ext. key 1316189175740, ext. key 1316190075762, ext. key 1316189238436, ext. key 1316189175741,
ext. key 1316190075763, ext. key 1316189238437, ext. key 1316189175743, ext. key 1316190075765,
ext. key 1316189238439, ext. key 1316189175742, ext. key 1316190075766, ext. key 1316189238438,
ext. key 1316189175744, ext. key 1316190075767, ext. key 1316189238440, ext. key 1316189175746,
ext. key 1316190075768, ext. key 1316189238441, ext. key 1316189175745, ext. key 1316190075769,
ext. key 1316189238442, ext. key 1316189175747, ext. key 1316190075770, ext. key 1316189238444,
ext. key 1316189175752, ext. key 1316190075774, ext. key 1316189238448, ext. key 1316189175750,
ext. key 1316190075771, ext. key 1316189238445, ext. key 1316189175749, ext. key 1316190075772,
ext. key 1316189238446, ext. key 1316189175751, ext. key 1316190075773, ext. key 1316189238447,
ext. key 1316189175748, ext. key 1316190075775, ext. key 1316189238449, ext. key 1316189175758,
ext. key 1316190075778, ext. key 1316189238451, ext. key 1316189175761, ext. key 1316190075776,
ext. key 1316189238450, ext. key 1316189175753, ext. key 1316190075777, ext. key 1316189238454,
ext. key 1316189175754, ext. key 1316190075779, ext. key 1316189238453, ext. key 1316189175760,
ext. key 1316190075783, ext. key 1316189238452, ext. key 1316189175764, ext. key 1316190075781,
ext. key 1316189238455, ext. key 1316189175762, ext. key 1316190075780, ext. key 1316189238456,
ext. key 1316189175763, ext. key 1316190075782, ext. key 1316189238457, ext. key 1316189175765,
ext. key 1316190075784, ext. key 1316189238458, ext. key 1316189175766, ext. key 1316190075785,
ext. key 1316189238459, ext. key 1316189175755, ext. key 1316190075786, ext. key 1316189238460,
ext. key 1316189175757, ext. key 1316190075787, ext. key 1316189238462, ext. key 1316189175756,
ext. key 1316190075788, ext. key 1316189238461, ext. key 1316189175768, ext. key 1316190075789,
ext. key 1316189238463, ext. key 1316189175767, ext. key 1316190075790, ext. key 1316189238464,
ext. key 1316189175759, ext. key 1316190075791, ext. key 1316189238465, ext. key 1316189175769,
ext. key 1316190075792, ext. key 1316189238466, ext. key 1316189175770, ext. key 1316190075793,
ext. key 1316189238467, ext. key 1316189175771, ext. key 1316190075794, ext. key 1316189238468,
ext. key 1316189175772, ext. key 1316190075795, ext. key 1316189238469, ext. key 1316189175773,
ext. key 1316190075796, ext. key 1316189238470, ext. key 1316189175774, ext. key 1316190075797,
ext. key 1316189238471, ext. key 1316189175778, ext. key 1316190075798, ext. key 1316189238472,
ext. key 1316189175776, ext. key 1316190075800, ext. key 1316189238474, ext. key 1316189175775,
ext. key 1316190075799, ext. key 1316189238473, ext. key 1316189175777, ext. key 1316190075801,
ext. key 1316189238475, ext. key 1316189175779, ext. key 1316190075802, ext. key 1316189238476,
ext. key 1316189175780, ext. key 1316190075803, ext. key 1316189238477, ext. key 1316189175781,
ext. key 1316190075804, ext. key 1316189238478, ext. key 1316189175782, ext. key 1316190075805,
ext. key 1316189238479, ext. key 1316189175783, ext. key 1316190075806, ext. key 1316189238480,
ext. key 1316189175784, ext. key 1316190075807, ext. key 1316189238481, ext. key 1316189175785,
ext. key 1316190075808, ext. key 1316189238482, ext. key 1316189175786, ext. key 1316190075809,
ext. key 1316189238483, ext. key 1316189175787, ext. key 1316190075810, ext. key 1316189238484,
ext. key 1316189175788, ext. key 1316190075811, ext. key 1316189238485]
Build info: version: '2.4.0', revision: '13336', time: '2011-08-17 21:21:21'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_26'
Driver info: driver.version: LoggingWebDriver
    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:131)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:105)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:407)
    at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:169)
    at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:93)
    at $Proxy24.get(Unknown Source)
    at org.openqa.selenium.support.events.EventFiringWebDriver.get(EventFiringWebDriver.java:144)

Reopened. Please report if the occurrences have decreased or increased with the release
of 2.6.0.

We have seen this drop to almost zero, however we did notice some occurrences whilst
modal security dialogs were present on the nodes (running Max OS X).

For me occurrences have decreased. 2.5 version used to fail 10/10 times. 2.6 fails 6/10
times. Error message that I see is:

     [java] Caused by: org.openqa.selenium.WebDriverException: Session [1316623164372]
not available - []; duration or timeout: 3 milliseconds
     [java] Build info: version: '2.6.0', revision: '13840', time: '2011-09-13 14:55:30'
     [java] System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-32-generic',
java.version: '1.6.0_24'
     [java] Driver info: driver.version: RemoteWebDriver
     [java]     at sun.reflect.GeneratedConstructorAccessor17.newInstance(Unknown Source)
     [java]     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     [java]     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     [java]     at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:147)
     [java]     at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:113)
     [java]     at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:397)
     [java]     at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:401)
     [java]     at org.openqa.selenium.remote.RemoteWebDriver.getTitle(RemoteWebDriver.java:160)
     [java]     at org.openqa.selenium.internal.seleniumemulation.GetTitle.handleSeleneseCommand(GetTitle.java:25)
     [java]     at org.openqa.selenium.internal.seleniumemulation.GetTitle.handleSeleneseCommand(GetTitle.java:1)
     [java]     at org.openqa.selenium.internal.seleniumemulation.SeleneseCommand.apply(SeleneseCommand.java:30)
     [java]     ... 18 more

I'm not sure if I am seeing the same thing, but there is definitely still something
wrong with grid 2.14.0 and running suites of tests via testNG (but I do not think it
is testNG).

I have a suite of tests, if I run them in parallel (4 nodes) they fail all the time
with various problems from missing elements to stale element exception to time outs.


If I restrict all the tests to only one thread all pass, also if I have 2 threads that
go to different URL's then all pass.

Now the conclusion I have drawn (although not 100% sure) is that there seems to be
some kind link between session and URL when running in parallel which causes the commands
to get lost..

Those of you seeing "Session not available" messages /must/ try grid 2.14.0 or higher.

This will print a message in the form of "Client requested session " + keyId + " that
was terminated due to " + somereason. This "reason" will tell us /why/ the session
is not available. There are a number of possible reasons,  the possible values ar 
       TIMEOUT,
ORPHAN,
CLIENT_STOPPED_SESSION,
FORWARDINGFAILED,
CREATIONFAILED,
PROXY_REREGISTRATION

@freynaud @nvidrum Comment #14 looks like the runaway session cleaner in remoteproxy
that we've been talking about.

#45: Can you please tell us if your tests work if you bypass the hub and run parallel
directly towards a node with for instance 4 threads ? Please also confirm that both
your clients, your hub and your nodes are running 2.14.0

my entire system was upgraded to 2.14.0, grid, nodes and client, i guess i just use
the node URL instead of the hub URL to bypass.

I hope this explains things, let me know if you need more.

Test1 - local test
capabilities = DesiredCapabilities.firefox();
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
WebDriver driver = new FirefoxDriver(capabilities);
driver.manage().window().setSize(new Dimension(1280, 800));
driver.get(targetURL);

Test2 - test against a grid node
capabilities = DesiredCapabilities.firefox();
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
WebDriver driver = new RemoteWebDriver(new URL("gridNode"), capabilities);
driver.manage().window().setSize(new Dimension(1280, 800));
driver.get(targetURL);

Test3 - test against the grid
capabilities = DesiredCapabilities.firefox();
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
WebDriver driver = new RemoteWebDriver(new URL("gridHub"), capabilities);
driver.manage().window().setSize(new Dimension(1280, 800));
driver.get(targetURL);


Testcase1 - All tests were performed with a simple test case that just logged onto
a web app.

A - 1 thread 1 class - All three tests pass
B - 1 thread 3 differrent classes - Test1 and Test2 pass - Test3;
session ext. key 1322764776981 has TIMED OUT and will be released

C - 3 thread 3 differrent classes - Test1 passed - Test2 (occasional fails) and Test3
failed if no nodes not released yet, pass if they are released checking against (http://10.14.0.7:4444/grid/console?config=true&configDebug=true)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="3" name="Parallel Test" parallel="tests" verbose="2">
  <test name="Simple Appliance Logon" preserve-order="true">
    <parameter name="propertyFile" value="test1.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest"/>
    </classes>
  </test>
  <test name="Simple Appliance Logon2" preserve-order="true">
    <parameter name="propertyFile" value="test2.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest1"/>
    </classes>
  </test>
  <test name="Simple Appliance Logon3" preserve-order="true">
    <parameter name="propertyFile" value="test3.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest2"/>
    </classes>
  </test>
</suite>

13:39:20.218 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764776998
13:40:25.220 WARN [22] org.openqa.grid.internal.RemoteProxy - session ext. key 1322764776999
has TIMED OUT and will be released
13:40:26.930 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764776999
13:40:26.931 WARN [22] org.openqa.grid.internal.RemoteProxy - session ext. key 1322764777000
has TIMED OUT and will be released
13:40:28.487 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764777000
13:40:33.489 WARN [22] org.openqa.grid.internal.RemoteProxy - session ext. key 1322764777001
has TIMED OUT and will be released
13:40:35.152 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764777001
13:41:45.155 WARN [22] org.openqa.grid.internal.RemoteProxy - session ext. key 1322764777002
has TIMED OUT and will be released
13:41:46.843 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764777002
13:41:51.844 WARN [22] org.openqa.grid.internal.RemoteProxy - session ext. key 1322764777003
has TIMED OUT and will be released
13:41:53.552 WARN [22] org.openqa.grid.selenium.proxy.DefaultRemoteProxy - Error releasing
the resources on timeout for session ext. key 1322764777003

D - 3 thread 3 identical classes - All three tests fail

by this i mean 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite thread-count="3" name="Parallel Test" parallel="tests" verbose="2">
  <test name="Simple Appliance Logon" preserve-order="true">
    <parameter name="propertyFile" value="test1.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest"/>
    </classes>
  </test>
  <test name="Simple Appliance Logon2" preserve-order="true">
    <parameter name="propertyFile" value="test2.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest"/>
    </classes>
  </test>
  <test name="Simple Appliance Logon3" preserve-order="true">
    <parameter name="propertyFile" value="test3.properties"/>
    <classes>
      <class name="selenium.appliance.smoketest.SimpleApplianceLogonTest"/>
    </classes>
  </test>
</suite>

I have similar issues with selenium 2.14: I 've got those "Session not found" and SocketExceptions
(WindowsXP and Firefox 8).
 As an attachment I have to JAVA examples. The first is a multithread example and I
don't know why I always get those errors. The second multisession example works always
but is not really suitable (maybe suitable when I try to use HashMaps and my own browserID).

@kristian.rosenvold@zenior.no where do you expect the message to be shown? RC or Hub
console?

After upgrading to 2.14, I could see the following extra message in the error

    <head>
     <title>Error 500 java.lang.reflect.InvocationTargetException</title>
     </head>
     <body>
     <h2>HTTP ERROR: 500</h2><pre>java.lang.reflect.InvocationTargetException</pre>
     <p>RequestURI=/wd/hub/session/1323192132284/title</p>
     <p><i><small><a href="http://jetty.mortbay.org">Powered by Jetty://</a></small></i></p>

     </body>
     </html>

Adding the remaining stack trace.

; duration or timeout: 1.07 seconds
     [java] Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
     [java] System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-33-generic',
java.version: '1.6.0_26'
     [java] Driver info: driver.version: RemoteWebDriver
     [java]     at sun.reflect.GeneratedConstructorAccessor18.newInstance(Unknown Source)
     [java]     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     [java]     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     [java]     at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:147)

We haven't seen this issue since upgrading to 2.14.0. I think we can safely say that
at least one cause for this has been resolved.

@dave.h   Please execute my two examples and see the exceptions! (with 2.14)

Hi We are still seeing this issue with 2.14

We run our tests on Chrome (verision 15) on Windows XP machine

Behavior that we see is exactly what Anand explained here

All, 
I have been running few tests continuously to see whether there is a pattern for this
failure. Here is what I have found

During the test, one of the requests will get timed out. From what I have seen, the
page doesn't load completely when this issue happens. This causes a node TIMEOUT to
happen. Hub would then send Delete Session command to the node, but that command doesn't
get any response from node. I could still see the browser open and waiting for the
page to load even after that delete session command was executed. 

We are not sure what is causing it to time out as the page does load with no issues.

I have the same problem with 2.15.

I also would like to add some info:

If I start a node with maxSession=4, I get "Session not available", same as others
explained. 

But if I start 4 nodes with maxSession=1, the grids distributes the jobs well and I
don't have any problems.

I have tested my examples (see above) and my tests failed now even with Selenium 2.16.
Sometimes I got a "UnreachableBrowserException" and sometimes only one browser window
was opened and the other threads will hang and cannot open a new browser window.
 But maybe someone has a working example test ( I used a google search) with concurrent
sessions or I'll have to wait for 2.17.

I have a different issue on similar lines with Selenium Grid 2.18.0 as well. I have
test which has a login screen with username/password. Grid actually writes on one browser
1st username and on 2nd browser 2nd username with 1st password and visa versa. Is this
a know problem with grid2 threading or am i missing something.
-----------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
  <suite name="TmSuite" parallel="tests" thread-count="5" verbose="1">
    <test name="Run on Firefox" preserve-order="true">
        <parameter name="browser" value="firefox"/>
            <classes>
                <class name="com.pri.tm.tests.Login"/>
            </classes>
    </test>
    <test name="Run on chrome" preserve-order="true">
        <parameter name="browser" value="chrome"/>
            <classes>
                <class name="com.pri.tm.tests.Login"/>
            </classes>
    </test>
        <test name="Run on IE" preserve-order="true">
        <parameter name="browser" value="iexplore"/>
            <classes>
                <class name="com.pri.tm.tests.Login"/>
            </classes>
    </test>
  </suite>
---------------------------

#60 & #61, your problems are probably both related to threading issues in your own code.
There are a /lot/ of people running far more concurrent set-ups than you describe without
any problems.

Ok, please provide an Java example code running 3 Firefox browsers (on the same computer)
searching Google. I did not get it to work.

This should be tested with r16033.

The timeout logic has been totally revised for 2.21. Please see the grid wiki page for
how to set this up.

The fix in 2.21 should solve the problem, and to the extent users stil experience timeout
related issues I recommend filing new issues, not attaching further "similar" symptoms
to this issue.

I am closing this issue now simply because it's turning into an epic; and it's fixed
for 2.21 ;)

I often get my tests hanged while running testng suite. Only resolution is to stop execution
and restart it again.

I am getting following error after executing Suite in as HUB and Client :

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.21.0', revision: '16552', time: '2012-04-11 19:08:38'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.7.0_05'
Driver info: driver.version: RemoteWebDriver
                at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:454)
                at org.openqa.selenium.remote.ExecuteMethod.execute(ExecuteMethod.java:47)
                at org.openqa.selenium.remote.RemoteMouse.mouseMove(RemoteMouse.java:89)
                at org.openqa.selenium.interactions.MoveMouseAction.perform(MoveMouseAction.java:37)
                at org.openqa.selenium.interactions.CompositeAction.perform(CompositeAction.java:32)
                at                 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.TestRunner.privateRun(TestRunner.java:767)
                at org.testng.TestRunner.run(TestRunner.java:617)
                at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
                at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
                at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
                at org.testng.SuiteRunner.run(SuiteRunner.java:240)
                at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
                at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
                at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
                at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
                at org.testng.TestNG.run(TestNG.java:1030)
                at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
                at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
                at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)
Caused by: java.net.SocketTimeoutException: Read timed out
                at java.net.SocketInputStream.socketRead0(Native Method)
                at java.net.SocketInputStream.read(Unknown Source)
                at java.net.SocketInputStream.read(Unknown Source)
                at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
                at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
                at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
                at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
                at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
                at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
                at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
                at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
                at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
                at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
                at org.apache.http.impl.cl

Hi,
I am using selenium grid 2 for executing the tests ,when I start both hub and node
in my system browser lanches but it lands in selenium help page with the following
message:You are using grid 2.24.1
Find help on the official selenium wiki : more help here
default monitoring page : console

But when my system is configured as only node and hub configured in other system browser
lanches and tests executes successfully in my system.Do i miss anything in my tests?

What are the commands you are giving to launch hub and node(client) in same machine?

frequently fails all of my tests

2.25.0
hub: Ubuntu 11.04
node:  Windows 7 Pro x64

Selenium::WebDriver::Error::UnknownError: Session [1348528030620] was terminated due
to CLIENT_STOPPED_SESSION (org.openqa.grid.common.exception.GridException)

Stack trace:
[remote server] org.openqa.grid.internal.ActiveTestSessions(ActiveTestSessions.java):104:in
`getExistingSession'
[remote server] org.openqa.grid.internal.Registry(Registry.java):423:in `getExistingSession'
[remote server] org.openqa.grid.web.servlet.handler.RequestHandler(RequestHandler.java):234:in
`getSession'
[remote server] org.openqa.grid.web.servlet.handler.RequestHandler(RequestHandler.java):116:in
`process'
[remote server] org.openqa.grid.web.servlet.DriverServlet(DriverServlet.java):84:in
`process'
[remote server] org.openqa.grid.web.servlet.DriverServlet(DriverServlet.java):68:in
`doPost'
[remote server] javax.servlet.http.HttpServlet(HttpServlet.java):727:in `service'
[remote server] javax.servlet.http.HttpServlet(HttpServlet.java):820:in `service'
[remote server] org.seleniumhq.jetty7.servlet.ServletHolder(ServletHolder.java):565:in
`handle'
[remote server] org.seleniumhq.jetty7.servlet.ServletHandler(ServletHandler.java):479:in
`doHandle'
[remote server] org.seleniumhq.jetty7.server.session.SessionHandler(SessionHandler.java):225:in
`doHandle'
[remote server] org.seleniumhq.jetty7.server.handler.ContextHandler(ContextHandler.java):1031:in
`doHandle'
[remote server] org.seleniumhq.jetty7.servlet.ServletHandler(ServletHandler.java):406:in
`doScope'
[remote server] org.seleniumhq.jetty7.server.session.SessionHandler(SessionHandler.java):186:in
`doScope'
[remote server] org.seleniumhq.jetty7.server.handler.ContextHandler(ContextHandler.java):965:in
`doScope'
[remote server] org.seleniumhq.jetty7.server.handler.ScopedHandler(ScopedHandler.java):117:in
`handle'
[remote server] org.seleniumhq.jetty7.server.handler.HandlerWrapper(HandlerWrapper.java):111:in
`handle'
[remote server] org.seleniumhq.jetty7.server.Server(Server.java):349:in `handle'
[remote server] org.seleniumhq.jetty7.server.AbstractHttpConnection(AbstractHttpConnection.java):452:in
`handleRequest'
[remote server] org.seleniumhq.jetty7.server.BlockingHttpConnection(BlockingHttpConnection.java):47:in
`handleRequest'
[remote server] org.seleniumhq.jetty7.server.AbstractHttpConnection(AbstractHttpConnection.java):894:in
`content'
[remote server] org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler(AbstractHttpConnection.java):948:in
`content'
[remote server] org.seleniumhq.jetty7.http.HttpParser(HttpParser.java):857:in `parseNext'
[remote server] org.seleniumhq.jetty7.http.HttpParser(HttpParser.java):230:in `parseAvailable'
[remote server] org.seleniumhq.jetty7.server.BlockingHttpConnection(BlockingHttpConnection.java):66:in
`handle'
[remote server] org.seleniumhq.jetty7.server.bio.SocketConnector$ConnectorEndPoint(SocketConnector.java):254:in
`run'
[remote server] org.seleniumhq.jetty7.util.thread.QueuedThreadPool(QueuedThreadPool.java):599:in
`runJob'
[remote server] org.seleniumhq.jetty7.util.thread.QueuedThreadPool$3(QueuedThreadPool.java):534:in
`run'
[remote server] java.lang.Thread(Thread.java):662:in `run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/response.rb:52:in
`assert_ok'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/response.rb:15:in
`initialize'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/http/common.rb:59:in
`new'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/http/common.rb:59:in
`create_response'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/http/default.rb:65:in
`request'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/http/common.rb:40:in
`call'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/bridge.rb:598:in
`raw_execute'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/bridge.rb:576:in
`execute'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/remote/bridge.rb:322:in
`executeScript'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/selenium-webdriver-2.25.0/lib/selenium/webdriver/common/driver.rb:211:in
`execute_script'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/watir-webdriver-0.6.1/lib/watir-webdriver/browser.rb:130:in
`execute_script'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/watir-webdriver-0.6.1/lib/watir-webdriver/browser.rb:125:in
`status'
/home/teamcity/hg/tatu/lib/site/common/site.rb:39:in `browser'
/home/teamcity/hg/tatu/spec/test_plan_197_spec.rb:235:in `block (3 levels) in <top
(required)>'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example.rb:113:in
`instance_eval'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example.rb:113:in
`block in run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example.rb:253:in
`with_around_each_hooks'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example.rb:110:in
`run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:378:in
`block in run_examples'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:374:in
`map'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:374:in
`run_examples'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:360:in
`run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:361:in
`block in run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:361:in
`map'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/example_group.rb:361:in
`run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/command_line.rb:28:in
`block (2 levels) in run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/command_line.rb:28:in
`map'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/command_line.rb:28:in
`block in run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/reporter.rb:34:in
`report'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/command_line.rb:25:in
`run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/runner.rb:69:in
`run'
/home/teamcity/hg/tatu/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.11.1/lib/rspec/core/runner.rb:8:in
`block in autorun'

hi,

we are using Selenium Grid Hub 1.0.18.

we are trying to execute a test suite. test suite contains many test cases. 

some times we are facing the below Error while close all browser keyword.

ERROR: There is no registered session with ID '991c9385d0a9412995a4fec6011d794f'. 
Either it timed out or you already closed it. 


Test Result 
-----------


KEYWORD: SeleniumLibrary.Capture Page Screenshot Products.png  
Documentation: Takes a screenshot of the current page and embeds it into the log. 
Start / End / Elapsed: 20130123 21:01:07.756 / 20130123 21:01:37.982 / 00:00:30.226


KEYWORD: SeleniumLibrary.Delete All Cookies  
Documentation: Deletes all cookies by calling `Delete Cookie` repeatedly. 
Start / End / Elapsed: 20130123 21:01:37.983 / 20130123 21:02:08.015 / 00:00:30.032


KEYWORD: SeleniumLibrary.Close All Browsers  
Documentation: Closes all open browsers and empties the connection cache. 
Start / End / Elapsed: 20130123 21:02:08.016 / 20130123 21:02:08.154 / 00:00:00.138



21:02:08.153 FAIL ERROR: There is no registered session with ID '991c9385d0a9412995a4fec6011d794f'.
 Either it timed out or you already closed it. 

Kindly anyone help us to resolve this issue.

Thanks in Advance.

-Karthik

@bskarthick Don't use grid hub version 1. It's unsupported and outdated.

Follow instructions at http://seleniumhq.org/download/ to use the latest 2.X version.

@kristian: The selenium grid page is still available, first hit for a google search
on "selenium grid" and does not metion anything about being deprecated, maybe as a
project member you could see to it that it is deleted or updated with a big warning
message not to use it?

http://selenium-grid.seleniumhq.org/

@kristian,

we are using selenium Grid Hub 1.0.18 in Unix boX in 4444 port.

we are regestering 4 selenium remote controls ports ( windows VM )to the above Grid
hub.

So kindly let me know do we need to update the selenium remote controls if we upgrade
selenium Grid Hub 2.x ??

Thanks in advance,

-Karthik