2 Requests Waiting For A Slot To Be Free

I have the same issue as Javier. Using the standalone server 2.2.0. It
hangs when I create a node on one machine which specifies a hub on a
different machine. After I run the command to start the node, I check
the grid/console webpage of my hub and it displays that it is
listening to my node momentarily. Upon refresh, it says (cannot rbe
reached at the moment). Creating a node on the same machine as the hub
works fine. I run the test case anyways (the hub is not listening to
nodes that are on the same machine) and here is the output. I tried
variations of nodes and hubs using standalone 2.2.0 and 2.1.0, and it
all seems to be the same problem. It seems to have know about the node
somehow because, if I run the node, it will hang, and eventually in
the hub's URL/grid/console webpage it say that the node cannot be
reached. However, if I kill the node, and rerun the same command
(using the same port I previously tried using with the node), in the
hub's terminal, it prints a warning saying:
WARNING: Proxy 'URL :htttp://192.168.10.1:7773/wd/hub time out :
300000' was previously registered. Cleaning up any stale test
sessions.
Thanks for the help in advanced!
-Daniel
On Jul 27, 11:30 pm, Krishnan Mahadevan

<krishnan.mahadevan1...@gmail.com> wrote:
> Javier, if the node is not available, I have seen the Grid throw back an
> error saying capability not present. I havent seen it wait.
>
> If the capability matching is indeed the problem, then you have a couple of
> options.
>
> 1. Spawn the webdriver node that is hooked to the hub with a nodeConfig file
> (u have to use the -nodeConfig parameter) and define capabilities such that
> the grid can redirect the request to the node.
> 2. Revisit your code, get away from using DesiredCapabilities c =
> DesiredCapabilities.internetExplorer() and instead use the following
>
> DesiredCapabilities c = new DesiredCapabilities();
> c.setBrowserName(DesiredCapabilites.internetExplore().getBrowserName());
>
> and then retry. Hope that helps.
>
> Thanks & Regards
> Krishnan Mahadevan
>
> 'All the desirable things in life are either illegal, expensive, fattening
> or in love with someone else!'
>
> On Wed, Jul 27, 2011 at 11:47 AM, Javier Garcia Paredero <
>
>
>
>
>
>
>

> garcia.pared...@gmail.com> wrote:
> > Yes. Actually if i open in the browserhttp://localhost:4444/grid/consoleIcan see the following

>
> > 1 requests waiting for a slot to be free.
>

> > - {platform=WINDOWS, ensureCleanSession=true, browserName=internet

> > explorer, version=9}
>
> > Looks like it cannot find the node
>
> > 2011/7/26 Eric Bass <3m8...@gmail.com>
>
> >> are you running the code below on the same machine that the hub is on? if
> >> not you should replace localhost with either the hostname or the IP address
> >> of the hub server.
>

> >> On Tue, Jul 26, 2011 at 8:34 AM, Javier Garcia <garcia.pared...@gmail.com

> >> > wrote:
>
> >>> Hi
>
> >>> I am trying to test using Grid2. I have an ie9 browser in a Windows7
> >>> VM
>
> >>> First i start the hub
> >>> java -jar selenium-server-standalone-2.2.0 -role hub
>
> >>> In the remote host i register the node
> >>> java -jar selenium-server-standalone-2.2.0.jar -role webdriver -

> >>> hubhttp://10.128.24.28:4444/grid/register-port 5556 -browser