why am I getting a client_gone exception

[Matt Westlake]

I cannot figure out why for the life of me this is happening. I am (at most) running 3 tests per node, and nowhere near running out of ram or cpu usage. I have tested using the "supported" firefox (23) on selenium (2.35) and chrome with chromedriver.

When running my ruby/cucumber tests in parallel using selenium grid, I often get the following error message:

    Session [eca6dabf-8f06-41e6-bb25-a6d46f380054] was terminated due to CLIENT_GONE (org.openqa.grid.common.exception.GridException)
[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):235:in `getSession'
      [remote server] org.openqa.grid.web.servlet.handler.RequestHandler(RequestHandler.java):117: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):62:in `doGet'
      [remote server] javax.servlet.http.HttpServlet(HttpServlet.java):707: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):884:in `headerComplete'
      [remote server] org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler(AbstractHttpConnection.java):938:in `headerComplete'
      [remote server] org.seleniumhq.jetty7.http.HttpParser(HttpParser.java):634: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'

[Sean Humbarger]

Did you ever get anywhere with this issue?  I'm running into the same problem.  Im using selenium grid 2.37.0.  My test works fine outside of grid, but as soon as I use grid, the test fails with the same error you described.

[Matt Westlake]

Sorry, no i have not gotten anywhere and it's annoying the crap out of me and causing a lot of problems at work.

[Krishnan Mahadevan]

Have you taken a look here : http://code.google.com/p/selenium/wiki/Grid2#Hub_diagnostic_messages

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/eb6f65aa-2154-4679-a755-471aa68e135a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Daniel Cadden]

We run selenium tests using four seperate grids (one per host) on Ubuntu Server 14.04.2 with vnc4server and Openbox. Tests are run on an automated schedule, upwards of 70 times each day.

We have been getting the CLIENT_GONE exception too, several times each day.

I found it coincided with the following exception on our Selenium Hubs:

WARN [4901] com.google.common.io.Closeables - IOException thrown while closing Closeable

And also coincided with the following exception on our Selenium Nodes:

WARN - Exception: Timed out waiting for page load.

I did a packet capture and found a Firefox instances was downloading the CISCO OpenH264 plugin at the time of the failure. I've disabled this plugin and set it not to be updated.

It's all rather circumstantial, but there's enough of a correlation as show likely cause and effect. Hopefully this will resolve the issue for us. (If not, I'll keep you posted).

For info, we are using selenium-server 2.45 and Firefox 35.0.1

​

Codeweavers April Newsletter l Benefits of upgrading to Codeweavers latest online finance solution



Codeweavers Ltd | Barn 4 | Dunston Business Village | Dunston | ST18 9AB
Registered in England and Wales No. 04092394 | VAT registration no. 974 9705 63 

Phone: 0800 021 0888  Email: contactus@codeweavers.net