Imran,
This usually happens when the Selenium Grid cleans out a session (Selenium Node to be specific).
So, I would request you to please take another look at the timeouts that you have defined at the selenium node and increase them. A lot of things have changed between Selenium 2 and Selenium 3.
The below should help you get oriented with the configurations.
12:33 $ java -jar selenium-server-standalone-3.14.0.jar -role node -help
Usage: <main class> [options]
 Options:
   --debug, -debug
     <Boolean> : enables LogLevel.FINE.
     Default: false
   --version, -version
     Displays the version and exits.
     Default: false
   -browserTimeout
     <Integer> in seconds : number of seconds a browser session is allowed to
     hang while a WebDriver command is running (example: driver.get(url)). If
     the timeout is reached while a WebDriver command is still processing,
     the session will quit. Minimum value is 60. An unspecified, zero, or
     negative value means wait indefinitely.
   -capabilities, -browser
     <String> : comma separated Capability values. Example: -capabilities
     browserName=firefox,platform=linux -capabilities
     browserName=chrome,platform=linux
   -cleanUpCycle
     <Integer> in ms : specifies how often the hub will poll running proxies
     for timed-out (i.e. hung) threads. Must also specify "timeout" option
   -custom
     <String> : comma separated key=value pairs for custom grid extensions.
     NOT RECOMMENDED -- may be deprecated in a future revision. Example:
     -custom myParamA=Value1,myParamB=Value2
   -downPollingLimit
     <Integer> : node is marked as "down" if the node hasn't responded after
     the number of checks specified in [downPollingLimit].
   -enablePlatformVerification
     <Boolean>: Whether or not to drop capabilities that does not belong to
     the current platform family. Defaults to true.
   -host
     <String> IP or hostname : usually determined automatically. Most
     commonly useful in exotic network configurations (e.g. network with VPN)
   -hub
     <String> : the url that will be used to post the registration request.
     This option takes precedence over -hubHost and -hubPort options.
   -hubHost
     <String> IP or hostname : the host address of the hub we're attempting
     to register with. If -hub is specified the -hubHost is determined from
     it.
   -hubPort
     <Integer> : the port of the hub we're attempting to register with. If
     -hub is specified the -hubPort is determined from it.
   -id
     <String> : optional unique identifier for the node. Defaults to the url
     of the remoteHost, when not specified.
   -jettyThreads, -jettyMaxThreads
     <Integer> : max number of threads for Jetty. An unspecified, zero, or
     negative value means the Jetty default value (200) will be used.
   -log
     <String> filename : the filename to use for logging. If omitted, will
     log to STDOUT
   -maxSession
     <Integer> max number of tests that can run at the same time on the node,
     irrespective of the browser used
   -nodeConfig
     <String> filename : JSON configuration file for the node. Overrides
     default values
   -nodePolling
     <Integer> in ms : specifies how often the hub will poll to see if the
     node is still responding.
   -nodeStatusCheckTimeout
     <Integer> in ms : connection/socket timeout, used for node "nodePolling"
     check.
   -port
     <Integer> : the port number the server will use.
   -proxy
     <String> : the class used to represent the node proxy. Default is
     [org.openqa.grid.selenium.proxy.DefaultRemoteProxy].
   -register
     if specified, node will attempt to re-register itself automatically with
     its known grid hub if the hub becomes unavailable.
   -registerCycle
     <Integer> in ms : specifies how often the node will try to register
     itself again. Allows administrator to restart the hub without restarting
     (or risk orphaning) registered nodes. Must be specified with the
     "-register" option.
   -remoteHost
     <String> URL: Address to report to the hub. Used to override default
     (http://<host>:<port>).
   -role
     <String> options are [hub], [node], or [standalone].
     Default: node
   -servlet, -servlets
     <String> : list of extra servlets the grid (hub or node) will make
     available. Specify multiple on the command line: -servlet
     tld.company.ServletA -servlet tld.company.ServletB. The servlet must
     exist in the path: /grid/admin/ServletA /grid/admin/ServletB
   -timeout, -sessionTimeout
     <Integer> in seconds : Specifies the timeout before the server
     automatically kills a session that hasn't had any activity in the last X
     seconds. The test slot will then be released for another test to use.
     This is typically used to take care of client crashes. For grid hub/node
     roles, cleanUpCycle must also be set.
   -unregisterIfStillDownAfter
     <Integer> in ms : if the node remains down for more than
     [unregisterIfStillDownAfter] ms, it will stop attempting to re-register
     from the hub.
   -withoutServlet, -withoutServlets
     <String> : list of default (hub or node) servlets to disable. Advanced
     use cases only. Not all default servlets can be disabled. Specify
     multiple on the command line: -withoutServlet tld.company.ServletA
     -withoutServlet tld.company.ServletB
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/
From: <selenium-***@googlegroups.com> on behalf of Imran Rahi <***@gmail.com>
Reply-To: <selenium-***@googlegroups.com>
Date: Tuesday, November 6, 2018 at 11:30 AM
To: Selenium Users <selenium-***@googlegroups.com>
Subject: [selenium-users] Selenium 3.12 - Session XX not available and is not among the last 1000 terminated
Hi All,
We recently upgraded to 3.12 from existing 2.53. We have a hub on linux and 10 nodes on windows.
After upgrade to 3.12 the most common errors we came across was
'Session [19b6e0db4ae161669734871baa4bffcb] not available and is not among the last 1000 terminated sessions'
The test are executed on Chrome 64 with driver 2.33.
We upgraded to 3.14 and 3.141 as well..but same errors. Finally we downgraded back to 2.53 and its working perfectly fine.
I conclude that 3.x version has this problem. But wanted to know others opinion as well.
The node and hub Conf file has been uploaded. Official names are replaced for host (no issue in connectivity)
Please advise.
Thanks,
--
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-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/a8334582-3525-4c7a-a09b-f1a96bdc4662%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/C1779AA6-BA3D-4BDB-84C4-DECF3D39FE91%40gmail.com.
For more options, visit https://groups.google.com/d/optout.