|
If you were logged in you would be able to see more operations.
|
|
|
Selenium Grid
Created: 13/Mar/08 02:17 AM
Updated: 14/Apr/08 09:36 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.0
|
| Fix Version/s: |
1.1
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Windows
|
|
|
Is selenium grid timing out when there are no actions being made to the browser in a certain period of time? And if so, is this timeout configurable?
I have a function that may take several minutes to execute, the behavior that I'm seeing is that after the function gets executed, none of the actions sent to the browser get made and the RC just remains stuck. This only happens if I use Selenium Grid though...
Example:
_activeBrowser.getLocation(); //gets executed successfully
Thread.sleep(120000);
System.
out.println("exited"); _activeBrowser.getLocation(); //doesn't get executed at all
|
|
Description
|
Is selenium grid timing out when there are no actions being made to the browser in a certain period of time? And if so, is this timeout configurable?
I have a function that may take several minutes to execute, the behavior that I'm seeing is that after the function gets executed, none of the actions sent to the browser get made and the RC just remains stuck. This only happens if I use Selenium Grid though...
Example:
_activeBrowser.getLocation(); //gets executed successfully
Thread.sleep(120000);
System.
out.println("exited"); _activeBrowser.getLocation(); //doesn't get executed at all
|
Show » |
|
Bug
Reopened
Major
Selenium Grid closes connection when test does not issue Selenium commands for some time. Make the timeout configurable.