I am always getting SessionCleanup after few hours. Because of the SessionCleanup, the test fails and Selenium is closed.
How do I stop executing SessionCleanup?
I found this but it is not fixed as mentioned:
http://code.google.com/p/selenium/issues/detail?id=3161
This error is in version 2.16.0 and 2.17.0
23.1.2012 9:48:52 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
23.1.2012 9:48:55 org.openqa.jetty.http.HttpServer doStart
INFO: Version Jetty/5.1.x
23.1.2012 9:48:55 org.openqa.jetty.util.FileResource <clinit>
INFO: Checking Resource aliases
23.1.2012 9:48:57 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.servlet.WebApplicationHandler@5e176f
23.1.2012 9:48:57 org.openqa.jetty.util.Container start
INFO: Started WebApplicationContext[/,/]
21.1.2012 9:48:57 org.openqa.jetty.http.SocketListener start
INFO: Started SocketListener on 0.0.0.0:4455
23.1.2012 9:48:57 org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.Server@1971afc
23.1.2012 12:59:22 SessionCleanup
WARNING: session ext. key 1327135735339 has TIMED OUT and will be released
You can control and maximize the
cleanupCycleat the client level when launching the node with the option-cleanupCycle 2147483647(Java MAX_INT). According to the documentation, it doesn’t look like you can prevent it entirely, but this will at least reduce the frequency to once every ~25 days if you have no other option.Execute your jar with this command to see more options:
java -jar selenium-server-standalone-2.16.0.jar -help