Selenium Hub incorrectly believes CLIENT_STOPPED_SESSION has happened

496 views
Skip to first unread message

robbiewinston

unread,
Oct 30, 2014, 3:50:00 PM10/30/14
to seleniu...@googlegroups.com

I am running parallel automated tests against a Selenium Grid.

Sometimes, a test with fail with;

Session [c1d99cc1-c689-4053-b68d-51c3682c13c4] was terminated due to CLIENT_STOPPED_SESSION (org.openqa.grid.common.exception.GridException)
[remote server] org.openqa.grid.internal.ActiveTestSessions(ActiveTestSessions.java):105:in `getExistingSession'

The Selenium documentation says;

CLIENT_STOPPED_SESSION  The session was stopped using an ordinary call to stop/quit on the client. Why are you using it again??

However, I know that the client has not attempted to stop/quit. I am using parallel rspec so each thread is actually it's own Ruby instance, so there is no issue test side.

Also, if I directly query the Node using http://{node_ip}:5556/wd/hub/static/resource/hub.html, I can see the session is still open. If quit/stop had been issued then, this session would have been deleted.

It would appear that it is only the Session Registry in the Selenium Grid Hub that thinks this session has been stopped. There is no evidence of the session being stopped anywhere else.

Is there a known issue with Grid where the incorrect session has been marked as stopped?

Joew

unread,
Jan 15, 2016, 9:22:01 AM1/15/16
to Selenium Users
Any luck finding a solution for this?

Krishnan Mahadevan

unread,
Jan 18, 2016, 5:32:40 AM1/18/16
to Selenium Users
Joe,
Do you have a reproducible test that can show this problem ?

You revived a very old thread and there is a good chance that a lot of things could have changed at the Grid side.

So please provide more info on the following :

Grid version that you are seeing this behavior with.
What does your test code look like.

I skimmed through the Grid codebase and as the error message says, the only time when a CLIENT_STOPPED_SESSION can come up as a Session Termination reason is when your test code invokes a driver.quit()





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/
My Technical Scribbings @ http://rationaleemotions.wordpress.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/1d42097d-97ff-4995-8a08-3dc391857568%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages