Skip to first unread message
Mike Riley
Sep 7, 2012, 4:15:43 PM9/7/12
to seleniu...@googlegroups.com
It would help to see how you have set up your grid server. What was the command line you use to start it, and please include the ones for your nodes as well.
It looks like you are using Linux on a PowerPC, so can I assume this is an old Mac system?
I did run into a problem where (apparently) memory leaks were happening somewhere in either the node or grid server. I resolved that in two ways:
After I did that I never had it hang that way again. I got a clue by watching the tests run on the remote server and seeing error messages come out about the time of the hang.
The error you are seeing means that the grid server is unable to communicate with the node server.
Mike
On Friday, September 7, 2012 4:29:38 AM UTC-7, Muhammad wrote:
It looks like you are using Linux on a PowerPC, so can I assume this is an old Mac system?
I did run into a problem where (apparently) memory leaks were happening somewhere in either the node or grid server. I resolved that in two ways:
- Used the java command line option to provide increased heap allocation.
- Used a Task Manager (Windows - cron for Linux) to restart the servers every day.
After I did that I never had it hang that way again. I got a clue by watching the tests run on the remote server and seeing error messages come out about the time of the hang.
The error you are seeing means that the grid server is unable to communicate with the node server.
Mike
On Friday, September 7, 2012 4:29:38 AM UTC-7, Muhammad wrote:
Hi all,
I am using Selenium version 2.15 and have set up a Grid, but it is very unstable and I can't really figure out why. Since I am not very experienced with Selenium and Selenium Grid, could you please help me?
I have a hub with the following configuration:Grid Hub 2.15.0
Config details :
hub launched with :-role hub -log /var/log/selenium_hub_log
the final configuration comes from :
the default :
host : null
port : 4444
cleanupCycle : 5000
timeout : 300000
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :
all params :
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
cleanUpCycle : 5000
host : null
maxSession : 5
newSessionWaitTimeout : -1
nodePolling : 5000
port : 4444
prioritizer : null
servlets : []
throwOnCapabilityNotPresent : true
timeout : 300000
updated with grid1 config :No grid1 file specified. To specify one, use -grid1Yml XXX.yml where XXX.yml is a grid1 config file
updated with grid2 config : No hub config file specified. To specify one, use -hubConfig XXX.json where XXX.json is a hub config file
updated with params :
host : null
port : 4444
cleanupCycle : 5000
timeout : 300000
newSessionWaitTimeout : -1
grid1Mapping : {}
throwOnCapabilityNotPresent : true
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
prioritizer : null
servlets :
all params :
log : /var/log/selenium_hub_log
role : hub
capabilityMatcher : org.openqa.grid.internal.utils.DefaultCapabilityMatcher
cleanUpCycle : 5000
host : null
maxSession : 5
newSessionWaitTimeout : -1
nodePolling : 5000
port : 4444
prioritizer : null
servlets : []
throwOnCapabilityNotPresent : true
timeout : 300000
I don't know whether it is related to the Grid configuration or not, but sometimes my selenium tests just pause for a very very long time (I am not sure whether they are pausing or waiting or hanging), but I can't determine the root cause of that.
For one particular test I get the following exception:
<html>
<head>
<title>Error 500 java.util.concurrent.RejectedExecutionException</title>
</head>
<body>
<h2>HTTP ERROR: 500</h2><pre>java.util.concurrent.RejectedExecutionException</pre>
<p>RequestURI=/wd/hub/session/1345824337169/element/51/click</p>
<p><i><small><a href="http://jetty.mortbay.org">Powered by Jetty://</a></small></i></p>
</body>
</html>
Command duration or timeout: 1969.44 seconds ( = 33min!!!)
Sometimes, for other tests I get the following error:
203 2012-08-08 06:20:37 WebDriverException caught. Caused by GridException
204 2012-08-08 06:20:37 |--'WebDriverException' Message: Error forwarding the new session Error forwarding the request Read timed out
205 Command duration or timeout: 10800.39 seconds
206 Build info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:56:25'
207 System info: os.name: 'Linux', os.arch: 'ppc64', os.version: '2.6.18-308.4.1.el5', java.version: '1.6.0'
208 Driver info: driver.version: RemoteWebDriver
209 2012-08-08 06:20:37 |--'GridException' Message: Error forwarding the new session Error forwarding the request Read timed out
210 2012-08-08 06:20:37 |--System Information: os.name: 'Linux', os.arch: 'ppc64', os.version: '2.6.18-308.4.1.el5', java.version: '1.6.0'
211 2012-08-08 06:20:37 |--Support URL: null
212 2012-08-08 06:20:37 |--Driver Information: driver.version: RemoteWebDriver
213 2012-08-08 06:20:37 \--Driver Name: RemoteWebDriver
214 2012-08-08 06:20:37 Caught exception: Error forwarding the new session Error forwarding the request Read timed out
215 Command duration or timeout: 10800.39 seconds ( = 3 hours -> this looks like a maximum timeout value)
216 Build info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:56:25'
217 System info: os.name: 'Linux', os.arch: 'ppc64', os.version: '2.6.18-308.4.1.el5', java.version: '1.6.0'
218 Driver info: driver.version: RemoteWebDriver
So far I have always tried to restart the grid components, and in most cases that worked, but took some time - sometimes :-D.
Since I haven't found any forum post with the same exceptions I turned the debug option and the log on, on both the grid and the nodes. But for me it is really sophisticated to read.
My question is: What is the right approach to debug such timeout problems, which entries in the selenium grid hub / node indicate a problem and where is the right place to look - you may have noticed my extensive use of "sometimes", but right now I am not understanding what is happening...
I really appreciate every help!
Muhammad
Sep 7, 2012, 6:53:28 PM9/7/12
to seleniu...@googlegroups.com
Hi Mike,
thanks very much for your reply.
Since the grid is maintained by another department and I haven't been involved in the setup of the grid, I am not sure which machines/platforms we are using, but the os is mainly LINUX. I'll post what I 've got already, If necessary I'll clarify on monday.
Here are some information for one node, I think the first two nodes are configured similarly, but the third runs an Internet Explorer, so it must be a WINDOWS machine:
24-Aug-2012 17:05:36 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid node
adding browserName=firefox,version=8.0.1,firefox_binary=/opt/browsers/firefox8.0.1/firefox,maxinstances=3,platform=LINUX
adding browserName=firefox,version=9.0.1,firefox_binary=/opt/browsers/firefox9.0.1/firefox,maxinstances=3,platform=LINUX
17:05:36.771 INFO - Java: IBM Corporation 2.4
17:05:36.773 INFO - OS: Linux 2.6.27.54-0.2-pae x86
17:05:36.781 INFO - v2.15.0, with Core v2.15.0. Built from revision 15105
17:05:36.903 INFO - RemoteWebDriver instances should connect to: http://127.0.0.2:5555/wd/hub
17:05:36.904 INFO - Version Jetty/5.1.x
17:05:36.906 INFO - Started HttpContext[/selenium-server,/selenium-server]
17:05:36.910 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@b7c0b7c
17:05:36.910 INFO - Started HttpContext[/wd,/wd]
17:05:36.910 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
17:05:36.910 INFO - Started HttpContext[/,/]
17:05:36.954 INFO - Started SocketListener on 0.0.0.0:5555
17:05:36.954 INFO - Started org.openqa.jetty.jetty.Server@9630963
17:05:36.956 INFO - using the json request : {"capabilities":[{"platform":"LINUX","browserName":"firefox","firefox_binary":"/opt/browsers/firefox8.0.1/firefox","version":"8.0.1","maxinstances":"3"},{"platform":"LINUX","browserName":"firefox","firefox_binary":"/opt/browsers/firefox9.0.1/firefox","version":"9.0.1","maxinstances":"3"}],"configuration":{"port":5555,"registerCycle":5000,"register":true,"host":"node1url","browser":"browserName=firefox,version=8.0.1,firefox_binary=/opt/browsers/firefox8.0.1/firefox,maxinstances=3,platform=LINUX","proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","remoteHost":"http://node1url:5555","url":"http://node1url:5555","maxSession":5,"hub":"http://hubURL:4444/grid/register","hubPort":4444,"role":"node","hubHost":"hubURL"},"class":"org.openqa.grid.common.RegistrationRequest"}
17:05:36.982 INFO - starting auto register thread. Will try to register every 5000 ms.
17:05:36.983 INFO - Registering the node to hub :http://hubURL:4444/grid/register
17:05:42.424 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@5f6a5f6a at URL: /status)
17:05:42.425 INFO - Done: /status
17:05:47.434 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@30143014 at URL: /status)
17:05:47.434 INFO - Done: /status
17:05:52.439 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@6bd46bd4 at URL: /status)
17:05:52.439 INFO - Done: /status
The hub's start command:
nohup /opt/ibm/ibm-java-ppc64-60/jre/bin/java -jar /opt/selenium/selenium-server-standalone-2.15.0.jar -role hub -log /var/log/selenium_hub_log &Some hub log entry:
Hub Log entries after start:
15:31:27.200 INFO [0] org.openqa.jetty.http.HttpServer - Version Jetty/5.1.x
15:31:27.220 INFO [0] org.openqa.jetty.util.Credential - Checking Resource aliases
15:31:27.965 INFO [0] org.openqa.jetty.util.Container - Started org.openqa.jetty.jetty.servlet.WebApplicationHandler@62346234
15:31:28.067 INFO [0] org.openqa.jetty.util.Container - Started WebApplicationContext[/,/]
15:31:28.076 INFO [0] org.openqa.jetty.http.SocketListener - Started SocketListener on 0.0.0.0:4444
15:31:28.077 INFO [0] org.openqa.jetty.util.Container - Started org.openqa.jetty.jetty.Server@5e785e78
15:31:30.407 WARN [1] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.410 WARN [1] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.525 WARN [2] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.527 WARN [2] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.817 WARN [3] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
As far as I am concerned the server running the grid components are highly utilized, I will ask my colleagues to check whether we are running out of memory or not.
Yeah, restarting the grid components, was the only way to get the grid working again, but shouldn't there be a better solution for the memory problem?
In my case I see the exception is thrown after the timeout is reached.
Where is it logged when a communication issue like that occurs? I would assume both on hub and node side?
On my local machine I am running a grid hub too and have set the "-debug" flag. When I modify the tests to use my local grid, instead of the remote one, I can only see relevant information in the node log (at least I think that they relevant) but not in the hub log
thanks very much for your reply.
Since the grid is maintained by another department and I haven't been involved in the setup of the grid, I am not sure which machines/platforms we are using, but the os is mainly LINUX. I'll post what I 've got already, If necessary I'll clarify on monday.
Here are some information for one node, I think the first two nodes are configured similarly, but the third runs an Internet Explorer, so it must be a WINDOWS machine:
24-Aug-2012 17:05:36 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid node
adding browserName=firefox,version=8.0.1,firefox_binary=/opt/browsers/firefox8.0.1/firefox,maxinstances=3,platform=LINUX
adding browserName=firefox,version=9.0.1,firefox_binary=/opt/browsers/firefox9.0.1/firefox,maxinstances=3,platform=LINUX
17:05:36.771 INFO - Java: IBM Corporation 2.4
17:05:36.773 INFO - OS: Linux 2.6.27.54-0.2-pae x86
17:05:36.781 INFO - v2.15.0, with Core v2.15.0. Built from revision 15105
17:05:36.903 INFO - RemoteWebDriver instances should connect to: http://127.0.0.2:5555/wd/hub
17:05:36.904 INFO - Version Jetty/5.1.x
17:05:36.906 INFO - Started HttpContext[/selenium-server,/selenium-server]
17:05:36.910 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@b7c0b7c
17:05:36.910 INFO - Started HttpContext[/wd,/wd]
17:05:36.910 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
17:05:36.910 INFO - Started HttpContext[/,/]
17:05:36.954 INFO - Started SocketListener on 0.0.0.0:5555
17:05:36.954 INFO - Started org.openqa.jetty.jetty.Server@9630963
17:05:36.956 INFO - using the json request : {"capabilities":[{"platform":"LINUX","browserName":"firefox","firefox_binary":"/opt/browsers/firefox8.0.1/firefox","version":"8.0.1","maxinstances":"3"},{"platform":"LINUX","browserName":"firefox","firefox_binary":"/opt/browsers/firefox9.0.1/firefox","version":"9.0.1","maxinstances":"3"}],"configuration":{"port":5555,"registerCycle":5000,"register":true,"host":"node1url","browser":"browserName=firefox,version=8.0.1,firefox_binary=/opt/browsers/firefox8.0.1/firefox,maxinstances=3,platform=LINUX","proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","remoteHost":"http://node1url:5555","url":"http://node1url:5555","maxSession":5,"hub":"http://hubURL:4444/grid/register","hubPort":4444,"role":"node","hubHost":"hubURL"},"class":"org.openqa.grid.common.RegistrationRequest"}
17:05:36.982 INFO - starting auto register thread. Will try to register every 5000 ms.
17:05:36.983 INFO - Registering the node to hub :http://hubURL:4444/grid/register
17:05:42.424 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@5f6a5f6a at URL: /status)
17:05:42.425 INFO - Done: /status
17:05:47.434 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@30143014 at URL: /status)
17:05:47.434 INFO - Done: /status
17:05:52.439 INFO - Executing: org.openqa.selenium.remote.server.handler.Status@6bd46bd4 at URL: /status)
17:05:52.439 INFO - Done: /status
The hub's start command:
nohup /opt/ibm/ibm-java-ppc64-60/jre/bin/java -jar /opt/selenium/selenium-server-standalone-2.15.0.jar -role hub -log /var/log/selenium_hub_log &Some hub log entry:
Hub Log entries after start:
15:31:27.200 INFO [0] org.openqa.jetty.http.HttpServer - Version Jetty/5.1.x
15:31:27.220 INFO [0] org.openqa.jetty.util.Credential - Checking Resource aliases
15:31:27.965 INFO [0] org.openqa.jetty.util.Container - Started org.openqa.jetty.jetty.servlet.WebApplicationHandler@62346234
15:31:28.067 INFO [0] org.openqa.jetty.util.Container - Started WebApplicationContext[/,/]
15:31:28.076 INFO [0] org.openqa.jetty.http.SocketListener - Started SocketListener on 0.0.0.0:4444
15:31:28.077 INFO [0] org.openqa.jetty.util.Container - Started org.openqa.jetty.jetty.Server@5e785e78
15:31:30.407 WARN [1] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.410 WARN [1] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.525 WARN [2] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.527 WARN [2] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
15:31:30.817 WARN [3] org.openqa.grid.internal.RemoteProxy - Max instance not specified. Using default = 1 instance
As far as I am concerned the server running the grid components are highly utilized, I will ask my colleagues to check whether we are running out of memory or not.
Yeah, restarting the grid components, was the only way to get the grid working again, but shouldn't there be a better solution for the memory problem?
In my case I see the exception is thrown after the timeout is reached.
Where is it logged when a communication issue like that occurs? I would assume both on hub and node side?
On my local machine I am running a grid hub too and have set the "-debug" flag. When I modify the tests to use my local grid, instead of the remote one, I can only see relevant information in the node log (at least I think that they relevant) but not in the hub log
Mike Riley
Sep 11, 2012, 1:35:02 AM9/11/12
to seleniu...@googlegroups.com
You are using a very old version that doesn't have all the current fixes, so I would update it to the current version. A lot of issues with memory leaks and the grid servers have been addressed since then. The current version is 2.25.0 now.
Mike
Mike
Muhammad
Sep 11, 2012, 4:31:32 AM9/11/12
to seleniu...@googlegroups.com
Hi Mike,
ok I will do that, and get back to you if the problem persists
Thanks very much!
ok I will do that, and get back to you if the problem persists
Thanks very much!
Muhammad
Sep 29, 2012, 7:12:17 AM9/29/12
to seleniu...@googlegroups.com
I noticed, that I get a 3 hour time out
when my WebDriver loses the connection to the session / hub and
the code tries to use it again:
4 2012-09-21 12:45:09
Timed out waiting for page load.
345 Command duration or timeout:
1800.04 seconds
346 Build info: version: '2.25.0', revision:
'17482', time: '2012-07-18 21:08:56'
347 System info: os.name:
'Windows Server 2008', os.arch: 'x86', os.version: '6.0 build 6001
Service Pack 1', java.version: '1.6.0'
348 Driver info:
driver.version: RemoteWebDriver
349 Session ID:
2d23ad91-fcfb-4c03-a31f-a07b3fb87ab3
350 Command duration or
timeout: 1800.32 seconds
351 Build info: version: '2.15.0',
revision: '15105', time: '2011-12-08 09:56:25'
352 System info:
os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version:
'1.6.0'
353 Driver info: driver.version: RemoteWebDriver
354
2012-09-21 12:45:09 Screenshot requested at URL
'http://hostname:7203/webui/'
355 2012-09-21 15:45:09
Unable to take screenshot.
org.openqa.selenium.remote.UnreachableBrowserException: Error
communicating with the remote browser. It may have died.
356 Build
info: version: '2.15.0', revision: '15105', time: '2011-12-08
09:56:25'
In my tests it was a default behavior to take a
screenshot after an exception has been thrown. But to take the
screenshot the code used the same driver object that threw the
timeout exception:
final WebDriver augmentedDriver = new
Augmenter().augment(getDriver());
if (augmentedDriver instanceof TakesScreenshot) {
I think,
after the time out exception the hub closed the session to the driver
that's why I get "Error communicating with the remote browser.
It may have died".
I changed my code to check the type of the
exception before attempting to take a screenshot - this solved the
problem.
But I still have a question:
Even after upgrading
to Selenium.2.25 I sometimes notice three hours timeouts. I think
they are all related to the hub trying to communicate with the nodes
/ browser:
2012-09-26 06:11:09 The test setup
passed.
186 2012-09-26 09:00:34 WebDriverException
caught. Caused by SocketException
187 2012-09-26 09:00:34
|--'WebDriverException' Message: Socket operation on nonsocket:
JVM_Bind
188 Command duration or timeout: 10165.39 seconds
189
Build info: version: '2.15.0', revision: '15105', time: '2011-12-08
09:56:25'
190 System info: os.name: 'Linux', os.arch: 'amd64',
os.version: '2.6.16.60-0.83.2-default', java.version: '1.6.0'
191
Driver info: driver.version: RemoteWebDriver
192 2012-09-26
09:00:34 |--'SocketException' Message: Socket
operation on nonsocket: JVM_Bind
193 2012-09-26 09:00:34
|--System Information: os.name: 'Linux', os.arch: 'amd64',
os.version: '2.6.16.60-0.83.2-default', java.version: '1.6.0'
194
2012-09-26 09:00:34 |--Support URL: null
195
2012-09-26 09:00:34 |--Driver Information:
driver.version: RemoteWebDriver
196 2012-09-26 09:00:34
\--Driver Name: RemoteWebDriver
After the output "The
test setup passed." I attempt to create a
RemoteWebDriver:
driver = new RemoteWebDriver(hub,
getCapability());
actualCapability = driver.getCapabilities();
I believe the 3
hour timeout is somehow a default selenium value for the
communication between grid and nodes (or for session handling).
Is
there anyway to change this timeout value with the selenium API?
François Reynaud
Oct 1, 2012, 6:28:46 PM10/1/12
to seleniu...@googlegroups.com
please update your nodes too. You seem to still use version: '2.15.0'
--To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/bCZ-cNG4JcYJ.
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
Muhammad
Oct 3, 2012, 6:49:04 AM10/3/12
to seleniu...@googlegroups.com
Francois, the selenium hub and the selenium hub nodes are using version 2.25 of the selenium-server-standalone.jar
Only the actual tests still use version 2.15 to send the commands.
Are there any known compatibility issues?
Also, could you please tell me if there is away to avoid the 3 hours timeout, or is that not a selenium setting?
Only the actual tests still use version 2.15 to send the commands.
Are there any known compatibility issues?
Also, could you please tell me if there is away to avoid the 3 hours timeout, or is that not a selenium setting?
Mike Riley
Oct 9, 2012, 4:50:52 PM10/9/12
to seleniu...@googlegroups.com
I used a hub with the latest version at the time (2.22 I think) and my nodes and test code used the 2.14 version and they seemed to run just fine. The key is that you need to use the correct communication between your task, the hub, and the nodes, which probably has not changed.
However, unless there is a compelling reason to stay with 2.15 on your nodes I would update them too. A lot of fixes for memory leaks and other issues have been done since that version. I stayed on 2.14 because of the mouseOver issue that was introduced in 2.15 and later, until I was able to code a workaround.
You can never be sure you won't run into an issue using mismatched versions of library+hub+node software, so better to have them all in sync.
Mike
However, unless there is a compelling reason to stay with 2.15 on your nodes I would update them too. A lot of fixes for memory leaks and other issues have been done since that version. I stayed on 2.14 because of the mouseOver issue that was introduced in 2.15 and later, until I was able to code a workaround.
You can never be sure you won't run into an issue using mismatched versions of library+hub+node software, so better to have them all in sync.
Mike
Muhammad
Oct 20, 2012, 6:03:10 AM10/20/12
to seleniu...@googlegroups.com
Hi all,
some updates on the issue:
Good News:
I have finally managed to upgraded the selenium version for the test code to 2.25, so now everything uses the same Selenium version.
Bad News:
However I still can get 3 hours timeouts sometimes when running the tests. Since the tests run over night and nobody can keep an eye on them, I can't effort such a long timeout.
Good News
I think I am able to tell how this issue can be reproduced now, because I experienced it 3 times live:
The timeout happens when the hub has established a session to the node and the test is about to start, but in that moment (I think before the test page is loaded) the node crashes. I know "crash" is not a very precise description but I am not sure what happens. However, from what I saw the session is neither terminated by the "crashed" node nor by the hub, and the selenium process on the node is still running. Just stopping the selenium node manually after a session has been established, will cause the session to be terminated and no 3 hours timeout will happen.
For me this looks like a defect, since nobody mentioned whether one can change this timeout or not.
Please, could you have a look at the following information that I gathered and help me determining what to do next:
The following Exception was thrown when I had a 3 hours timeout:
2012-10-13 14:10:35 Requesting capability: internet explorer on WINDOWS
2012-10-13 17:10:35 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-13 17:10:35 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-71.29.1.el6.x86_64', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver
2012-10-13 17:10:35 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-71.29.1.el6.x86_64', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:462)
at com.webadmin.viewer.rrr_webui_viewer.rrr_webui_viewer_filter_7(rrr_webui_viewer.java:493)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)mbte
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more
I could find the following in the hub log:
14:12:51.629 WARN [52] org.openqa.grid.internal.Registry - Proxy 'host :http://autun.v6.com:5555 time out : 300000' was previously registered. Cleaning up any stale test sessions.
15:01:48.368 ERROR [53] org.openqa.grid.web.servlet.handler.RequestHandler - cannot forward the request Connection reset
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:179)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.co2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 morenn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:776)
at org.openqa.grid.internal.TestSession.sendRequestToNode(TestSession.java:318)
at org.openqa.grid.internal.TestSession.forward(TestSession.java:221)
at org.openqa.grid.web.servlet.handler.RequestHandler.forwardRequest(RequestHandler.java:95)
at org.openqa.grid.web.servlet.handler.RequestHandler.process(RequestHandler.java:126)
at org.openqa.grid.web.servlet.DriverServlet.process(DriverServlet.java:84)
at org.openqa.grid.web.servlet.DriverServlet.doPost(DriverServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.seleniumhq.jetty7.servlet.ServletHolder.handle(ServletHolder.java:565)
at org.seleniumhq.jetty7.servlet.ServletHandler.doHandle(ServletHandler.java:479)
at org.seleniumhq.jetty7.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at org.seleniumhq.jetty7.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
at org.seleniumhq.jetty7.servlet.ServletHandler.doScope(ServletHandler.java:406)
at org.seleniumhq.jetty7.server.session.SessionHandler.doScope(SessionHandler.java:186)
at org.seleniumhq.jetty7.server.handler.ContextHandler.doScope(ContextHandler.java:965)
at org.seleniumhq.jetty7.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.seleniumhq.jetty7.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.seleniumhq.jetty7.server.Server.handle(Server.java:349)
at org.seleniumhq.jetty7.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
at org.seleniumhq.jetty7.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)
at org.seleniumhq.jetty7.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
at org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
at org.seleniumhq.jetty7.http.HttpParser.parseNext(HttpParser.java:857)
at org.seleniumhq.jetty7.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.seleniumhq.jetty7.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)
at org.seleniumhq.jetty7.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)
at org.seleniumhq.jetty7.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at org.seleniumhq.jetty7.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Thread.java:736)
another Example, unfortunately I have no hub log entry for this:
2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more
Thanks everybody, your help is very much appriciated
some updates on the issue:
Good News:
I have finally managed to upgraded the selenium version for the test code to 2.25, so now everything uses the same Selenium version.
Bad News:
However I still can get 3 hours timeouts sometimes when running the tests. Since the tests run over night and nobody can keep an eye on them, I can't effort such a long timeout.
Good News
I think I am able to tell how this issue can be reproduced now, because I experienced it 3 times live:
The timeout happens when the hub has established a session to the node and the test is about to start, but in that moment (I think before the test page is loaded) the node crashes. I know "crash" is not a very precise description but I am not sure what happens. However, from what I saw the session is neither terminated by the "crashed" node nor by the hub, and the selenium process on the node is still running. Just stopping the selenium node manually after a session has been established, will cause the session to be terminated and no 3 hours timeout will happen.
For me this looks like a defect, since nobody mentioned whether one can change this timeout or not.
Please, could you have a look at the following information that I gathered and help me determining what to do next:
The following Exception was thrown when I had a 3 hours timeout:
2012-10-13 14:10:35 Requesting capability: internet explorer on WINDOWS
2012-10-13 17:10:35 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-13 17:10:35 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Driver info: driver.version: RemoteWebDriver
2012-10-13 17:10:35 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:462)
at com.webadmin.viewer.rrr_webui_viewer.rrr_webui_viewer_filter_7(rrr_webui_viewer.java:493)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)mbte
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more
I could find the following in the hub log:
14:12:51.629 WARN [52] org.openqa.grid.internal.Registry - Proxy 'host :http://autun.v6.com:5555 time out : 300000' was previously registered. Cleaning up any stale test sessions.
15:01:48.368 ERROR [53] org.openqa.grid.web.servlet.handler.RequestHandler - cannot forward the request Connection reset
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:179)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.co2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverBuild info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverat org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverBuild info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverat org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 morenn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:776)
at org.openqa.grid.internal.TestSession.sendRequestToNode(TestSession.java:318)
at org.openqa.grid.internal.TestSession.forward(TestSession.java:221)
at org.openqa.grid.web.servlet.handler.RequestHandler.forwardRequest(RequestHandler.java:95)
at org.openqa.grid.web.servlet.handler.RequestHandler.process(RequestHandler.java:126)
at org.openqa.grid.web.servlet.DriverServlet.process(DriverServlet.java:84)
at org.openqa.grid.web.servlet.DriverServlet.doPost(DriverServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.seleniumhq.jetty7.servlet.ServletHolder.handle(ServletHolder.java:565)
at org.seleniumhq.jetty7.servlet.ServletHandler.doHandle(ServletHandler.java:479)
at org.seleniumhq.jetty7.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at org.seleniumhq.jetty7.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
at org.seleniumhq.jetty7.servlet.ServletHandler.doScope(ServletHandler.java:406)
at org.seleniumhq.jetty7.server.session.SessionHandler.doScope(SessionHandler.java:186)
at org.seleniumhq.jetty7.server.handler.ContextHandler.doScope(ContextHandler.java:965)
at org.seleniumhq.jetty7.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.seleniumhq.jetty7.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.seleniumhq.jetty7.server.Server.handle(Server.java:349)
at org.seleniumhq.jetty7.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
at org.seleniumhq.jetty7.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)
at org.seleniumhq.jetty7.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
at org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
at org.seleniumhq.jetty7.http.HttpParser.parseNext(HttpParser.java:857)
at org.seleniumhq.jetty7.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.seleniumhq.jetty7.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)
at org.seleniumhq.jetty7.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)
at org.seleniumhq.jetty7.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at org.seleniumhq.jetty7.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Thread.java:736)
another Example, unfortunately I have no hub log entry for this:
2012-10-19 08:13:34 Requesting capability: firefox on LINUX
2012-10-19 11:13:34 UnreachableBrowserException caught. Caused by SocketTimeoutException
2012-10-19 11:13:34 |--'UnreachableBrowserException' Message: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverBuild info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver2012-10-19 11:13:34 Stack trace was:
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'AIX', os.arch: 'ppc64', os.version: '7.1', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriverat org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:128)
at com.webadmin.SeleniumTestCase.getDriver(SeleniumTestCase.java:457)
at com.webadmin.login.webadmin_ui_login.webadmin_ui_login_1(webadmin_ui_login.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.webadmin.JarClassLoader.tryToInvokeMethod(JarClassLoader.java:191)
at com.webadmin.JarClassLoader.invokeClass(JarClassLoader.java:136)
at com.webadmin.TestScript.run_tests(TestScript.java:338)
at com.webadmin.webadmin.main(webadmin.java:86)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:216)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 13 more
Thanks everybody, your help is very much appriciated
Mike Riley
Oct 22, 2012, 4:14:29 PM10/22/12
to seleniu...@googlegroups.com
First let us fix your node invocation. I never define the location for the driver EXE files like you did, because I simply have them in a directory in my PATH for the system, so I can't say if those are correct or not. However, you only use one -role switch for the node, not one for every browser you support. So it should look something like this:
Note I changed the port to 4445, so it is just one off from the hub. If your nodes run on completely different systems than the grid you can use 4444 for them, too.
I think the problem with your running these in parallel is that you have your driver as a static instance, so there is only one copy shared by all the classes. So the second thread will overwrite the first instance that was created and the first one to finish will do a quit and all the other threads now are trying to talk to a closed session. Also, all your threads end up using whichever was the last session to be created.
You need to provide a way to have a unique session version of driver for each test thread you start.
I have never had to do that, but I sure others have posted how they did it here in the forum.
Mike
On Friday, October 19, 2012 6:27:55 AM UTC-7, Rao wrote:
C:\>java -jar selenium-server-standalone-2.25.0.jar -role webdriver -hub http://localhost:4444/grid/register -port 4445 -Dwebdriver.chrome.driver=C:\chromedriver\chromedriver.exe -browser "platform=WINDOWS,browserName=chrome,maxInstances=5" -browser "browserName=firefox,maxInstances=10" -Dwebdriver.ie.driver=C:\IEDriverServer\IEDriverServer.exe -browser "browserName=internet explorer,maxInstances=1"
I think the problem with your running these in parallel is that you have your driver as a static instance, so there is only one copy shared by all the classes. So the second thread will overwrite the first instance that was created and the first one to finish will do a quit and all the other threads now are trying to talk to a closed session. Also, all your threads end up using whichever was the last session to be created.
You need to provide a way to have a unique session version of driver for each test thread you start.
I have never had to do that, but I sure others have posted how they did it here in the forum.
Mike
On Friday, October 19, 2012 6:27:55 AM UTC-7, Rao wrote:
Hello Mike ,I am very new to Grid2 , I started the Grid2 from one cmd like belowC:\>java -jar selenium-server-standalone-2.25.0.jar -role hub http://localhost -port 4444and i registered my nodes to the HUB from another cmd like belowC:\>java -jar selenium-server-standalone-2.25.0.jar -Dwebdriver.chrome.driver=C:\chromedriver\chromedriver.exe -role webdriver -hub http://localhost:4444/grid/register -port 5558 -browser "platform=WINDOWS,browserName=chrome,maxInstances=5" -browser "browserName=firefox,maxInstances=10" -Dwebdriver.ie.driver=C:\IEDriverServer\IEDriverServer.exe -role webdriver -hub http://localhost:4444/grid/register -port 5559 -browser "browserName=internet explorer,maxInstances=1"I am trying to run my single test class in parallel , i am able to open the browsers with out any problem when i am trying to quit the browser i am getting the below exception
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
Below is my Testclassimport base.TestBase;import test.Consts;public class TestApp2 extends TestBase {@Testpublic void Test1() throws InterruptedException, MalformedURLException{loadWebSite(Consts.TEST_SITE_NAME);}}My TestBase class is like belowpublic class TestBase {public static WebDriver driver =null;@BeforeClass(alwaysRun =true)@Parameters ({"browsername"})public void setup(String browser) throws MalformedURLException{DesiredCapabilities cap = new DesiredCapabilities() ;if (browser.equalsIgnoreCase("firefox")){cap.setBrowserName(DesiredCapabilities.firefox().getBrowserName());}if (browser.equalsIgnoreCase("iexplorer")){cap.setBrowserName(DesiredCapabilities.internetExplorer().getBrowserName());}if (browser.equalsIgnoreCase("chrome")){cap.setBrowserName(DesiredCapabilities.chrome().getBrowserName());}driver = new RemoteWebDriver( new URL("http://localhost:4444/wd/hub"),cap);}public static void loadWebSite(String siteName) {driver.get(siteName);}@AfterTestpublic void quit(){driver.quit();}}please help regarding thisadvanced thanksRao
Rao
Oct 24, 2012, 4:36:36 AM10/24/12
to seleniu...@googlegroups.com
Hello Mike,
Thanks for your help in correcting me for the node invocation, as you suggested I have declared my driver as below
public RemoteWebDriver driver =null;
When i tried to use below method in my Testbase
@AfterClass
public void quit() throws MalformedURLException{
driver.quit();
}
I am getting the below error message in my Failed Tests
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_03'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:502)
at org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:372)
at base.TestBase.quit(TestBase.java:387)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:225)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.openqa.selenium.WebDriverException: Session ID may not be null
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:08:56'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_03'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.get(HttpCommandExecutor.java:560)
at org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.getMethod(HttpCommandExecutor.java:544)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:281)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
... 16 more
Mike please help me regarding this
Advanced Thanks
Rao
Muhammad
Oct 24, 2012, 7:46:30 AM10/24/12
to seleniu...@googlegroups.com
Hi Rao,
it looks like your problem is not related to timeout problems with the grid.
I mean no offence, but having two unrelated problems and stack traces in one topic, makes it hard for me (and I think for other people too) to see what we are discussing at the moment.
I mean no offence, but having two unrelated problems and stack traces in one topic, makes it hard for me (and I think for other people too) to see what we are discussing at the moment.
Would you mind opening a new topic for your problem, please?
The 3 hours timeout is really an issue for me and I can really figure out what causes it. If you have any suggestions, please let me know!
Thanks in advanced
Muhammad
Mike Riley
Oct 24, 2012, 1:04:07 PM10/24/12
to seleniu...@googlegroups.com
Hi Rao,
This error generally means that your session has already been closed. It can happen if you already did something in your code to terminate it, but it can also happen if the session is closed by the server.
The server will end the session if it sees no activity for something like 30 seconds (I think that is the default). I have had that happen when I am debugging my code and wait too long before letting it continue, for example.
Any chance that either of those conditions might have happened?
Try looking at the browser as your test runs and you might see the cause. You should also watch for messages being output by the server, because sometimes that will tell you what happened.
Mike
This error generally means that your session has already been closed. It can happen if you already did something in your code to terminate it, but it can also happen if the session is closed by the server.
The server will end the session if it sees no activity for something like 30 seconds (I think that is the default). I have had that happen when I am debugging my code and wait too long before letting it continue, for example.
Any chance that either of those conditions might have happened?
Try looking at the browser as your test runs and you might see the cause. You should also watch for messages being output by the server, because sometimes that will tell you what happened.
Mike
Philip Morby
Nov 19, 2012, 9:03:13 AM11/19/12
to seleniu...@googlegroups.com
Hello again!
Done some further digging and found this:
http://code.google.com/p/selenium/issues/detail?id=3951&q=3%20hour%20timeout&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary
Seems like we're not the only one hitting this issue, which is kind of good to know!
Done some further digging and found this:
http://code.google.com/p/selenium/issues/detail?id=3951&q=3%20hour%20timeout&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary
Seems like we're not the only one hitting this issue, which is kind of good to know!
Reply all
Reply to author
Forward
0 new messages