search

aimmac23 / selenium-reliable-node-plugin

Selenium Grid plugin to make the Grid more resilient to broken nodes
MIT License
1 stars 0 forks source link

Node tester doesn't work well for nodes with multiple configurations, but can only run one test in parallel #1

Closed aimmac23 closed 10 years ago

aimmac23 commented 10 years ago

Gives this stack trace, after testing the first slot:

[Thread-14] 2014/05/06 07:49:51.0521 [org.openqa.grid.internal.BaseRemoteProxy.getNewSession] -[INFO] - Node host :http://192.168.27.10:7771 has no free slots [Thread-25] 2014/05/06 07:49:51.0521 [org.openqa.grid.internal.Registry.release] -[WARNING] - Tried to release session with internal key 07febfdc-ec9e-4810-8a1c-1896b7bf10c4 but couldn't find it. 2014-05-06 19:49:51.522:WARN:osjs.ServletHandler:/grid/admin/NodeTestingServlet/session java.lang.NullPointerException at com.mooo.aimmac23.hub.servlet.NodeTestingServlet.doPost(NodeTestingServlet.java:53) 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) at java.lang.Thread.run(Thread.java:662)

aimmac23 commented 10 years ago

Fixed this one in version 0.5 - we simply sleep for a short time-period, then put the node-test back on the testing queue (a up to a certain number of times).