Open lukeis opened 8 years ago
lukeis
commented
8 years ago Please provide a complete executable scenario and a complete sample page to reproduce
the issue Reported by barancev on 2014-03-13 19:36:12
NeedsClarificationlukeis
commented
8 years ago Hi Alex!
The source code for the first problem:
WebElement price_w = driver.findElement(By.xpath("//input[contains(@id, '_price')]"));
Relevant web element on HTML page:
<input maxlength="6" name="SaleBusiness[price]" id="SaleBusiness_price" class="input-mini"
type="text" value="8500">
Problem number two happens after a 'TimeoutException'.
Both 2 problems happens only once, and hand reproducible. Please, ask if some additional
info is needed.Reported by bushevuv on 2014-03-13 20:16:17
lukeis
commented
8 years ago Another issue that is directly or indirectly related to the upgrade.
Unable to start WebDriver. org.openqa.selenium.WebDriverException: Unable to bind to
locking port 7054 within 10000 ms
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'ubuntu', ip: '91.105.232.144', os.name: 'Linux', os.arch: 'amd64',
os.version: '3.5.0-23-generic', java.version: '1.7.0_25'
Driver info: driver.version: RmDriver
at org.openqa.selenium.internal.SocketLock.lock(SocketLock.java:98)
at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:84)
at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:247)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:112)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:192)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:187)
at ru.manager.common.RmDriver.FFDriver(RmDriver.java:255)
at ru.manager.common.RmDriver.<init>(RmDriver.java:41)
at ru.manager.common.RmDriver.getInstance(RmDriver.java:293)
at ru.manager.common.CheckIP.checkByWhatisMyIpaddress(CheckIP.java:99)
at ru.manager.common.CheckIP.run(CheckIP.java:37)
at com.manager.editor.Editor.run(Editor.java:105)
at ru.manager.seleniumrunner.Main.main(Main.java:95)
Code part:
for (int i = 0; i < 50; i++) {
try {
driver = new FirefoxDriver(firefox, profile, cap);
driverIsStarted = true;
break;
} catch (WebDriverException ex) {
ex.printStackTrace(new PrintWriter(errors));
try {
Thread.sleep(5000);
} catch (InterruptedException e) {
break;
}
}
}
I want to note that before this update about a month this part of the code is always
beat stable.
Reported by bushevuv on 2014-03-14 09:51:03
lukeis
commented
8 years ago About the last comment: no it is not related to the upgrade. When you start a new FirefoxDriver
it sets a socket lock until the browser is fully up and running. If it can't set the
lock because another driver is starting and the socket is already locked it waits but
not too long. If you try to start many instances at once they fire browsers one by
one, while others are waiting. And as soon as one of them hits the timeout it thows
an exception "unable to bind to the locking port". See [1] for more detaled explanation.
[1] https://code.google.com/p/selenium/wiki/FirefoxDriverInternals#Flow_of_Control:_Starting_FirefoxReported by barancev on 2014-03-14 18:51:46
lukeis
commented
8 years ago Hi,
yes, I know that. I used for loop with sleeping for the synchronization porpose, it's
works fine for me.Reported by bushevuv on 2014-03-14 18:54:31
lukeis
commented
8 years ago So I suppose the reason to fail is increased startup time of a new Firefox version.
Unfortunately there is not enough information to understand what caused the browser
to hang. And the issue can't be reproduced deterministically.
Next time you see it hanging please open the browser error console (Ctrl-Shift-J) and
watch for error messages. This could help us much more than the client side stack trace
(that only can tell what operation hangs).Reported by barancev on 2014-03-14 18:56:20
Invalidlukeis
commented
8 years ago Hi,
ok. I will try to collcet requested information! Thank you/Reported by bushevuv on 2014-03-14 19:05:21
lukeis
commented
8 years ago Hi, please find a requested info in attachments.Reported by bushevuv on 2014-04-11 11:46:22
lukeis
commented
8 years ago The attached log is totally unrelated to "Unable to bind to locking port 7054", this
error means that selenium can't establish connection to the browser, and as a result
it can't send any command, contrary to what I can see in the log.Reported by barancev on 2014-04-11 12:53:28
lukeis
commented
8 years ago Yes, this problem is related to "hang on getScreenshotAs". (callstack number 2 in initial
problem description)Reported by bushevuv on 2014-04-11 13:06:55
lukeis
commented
8 years ago Ah, I see, reopening. Seems to be an attempt to take a shot when an alert is open.Reported by barancev on 2014-04-11 13:14:44
Newlukeis
commented
8 years ago Reported by luke.semerau on 2015-09-17 17:46:33
Originally reported on Google Code with ID 7090
Reported by
bushevuvon 2014-03-13 12:26:58