I am currently working with a selenium grid that has the following configuration:
{
"port": 4444,
"newSessionWaitTimeout": 2000
}
There are also 2 nodes that use this configuration:
{
"capabilities": [{
"browserName": "chrome",
"platform": "LINUX",
"maxInstances": 8
}],
"configuration": {
"nodeTimeout": 120,
"port": 5555,
"hubPort": 4444,
"hubHost": "hubhost",
"nodePolling": 2000,
"registerCycle": 10000,
"register": true,
"cleanUpCycle": 2000,
"timeout": -1,
"browserTimeout": -1,
"maxSession": 8
}
}
I have written a Java code that establishes a connection using the RemoteWebDriver-Class. The code performs various actions on the driver and then goes into a suspended state for an unknown duration (between 30 seconds to 1 hour). I need the session to remain open as the process needs to quickly resume upon waking up.
When the timeout is set to -1, everything works fine. The process stays connected to the session and the browser indefinitely. However, at times the process gets terminated randomly by an automated service. The node acknowledges the client shutdown with the message:
selenium deleted due to client timeout
But the sessions are not cleaned up! The unlimited timeout keeps them alive and the grid doesn't release them for further use.
Is there a solution within the selenium config to address this issue?
Implementing a process-shutdown-hook that calls "driver.quit()" to release the session is not desirable in my case.
Any suggestions or assistance would be greatly appreciated. Thank you!