Session not available error

35 views
Skip to first unread message

Payal Gupta

unread,
May 10, 2012, 8:04:33 AM5/10/12
to webd...@googlegroups.com, seleniu...@googlegroups.com
Hi All,

I am getting following error while executing the TCs on virtual machines. I have cross checked grid console settings and connection seems proper to me.
Does anyone have an idea, what else can cause this error ?


Caused by: org.openqa.grid.common.exception.GridException: Session [1336540865034] not available - []
        at org.openqa.grid.web.servlet.handler.RequestHandler.process(RequestHandler.java:163)
        at org.openqa.grid.web.servlet.DriverServlet.process(DriverServlet.java:81)
        at org.openqa.grid.web.servlet.DriverServlet.doPost(DriverServlet.java:67)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.openqa.jetty.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
        at org.openqa.jetty.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
        at org.openqa.jetty.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
        at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
        at org.openqa.jetty.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
        at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
        at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
        at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
        at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
        at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
        at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
        at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
        at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:98)
        at java.io.BufferedWriter.write(BufferedWriter.java:203)
        at java.io.Writer.write(Writer.java:140)

Running Failed: 0
        at com.disney.studios.dsaa.qa.util.ReportHTML.writeTrailer(ReportHTML.java:153)
        at com.disney.studios.dsaa.qa.util.Report.close(Report.java:141)
        at com.disney.studios.dsaa.qa.scenarios.DSAARun.processTestCases(DSAARun.java:518)
        at com.disney.studios.dsaa.qa.scenarios.RunTestScenario.runScenario(RunTestScenario.java:34)
        at com.disney.studios.dsaa.qa.scenarios.TestW7FF4.testBrowser1(TestW7FF4.java:14)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Running Passed: 0




Krishnan Mahadevan

unread,
May 10, 2012, 8:07:45 AM5/10/12
to webd...@googlegroups.com
The Grid cleaned up the session with ID " 1336540865034 " due to a timeout or idle browser state, and your testcode still has a reference to it and you tried accessing that particular session (A session is mostly mapped backed to a browser instance, so in your case, the grid cleaned up a browser and you still assume you have a reference to it)


Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"




--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To post to this group, send email to webd...@googlegroups.com.
To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

Payal Gupta

unread,
May 10, 2012, 8:09:01 AM5/10/12
to webd...@googlegroups.com
What can cause the cleaning up of session id ?

Krishnan Mahadevan

unread,
May 10, 2012, 8:13:27 AM5/10/12
to webd...@googlegroups.com
Like I said, earlier,

You may have caused a browser being idle long enough that the Grid regarded the browser as no longer required and closed it (or)
somewhere in your testcase you closed the browser by calling a driver.quit() or driver.close() and then you tried accessing the browser via that driver instance.

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"



Reply all
Reply to author
Forward
0 new messages