You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.
What steps will reproduce the problem?
/usr/bin/java -jar /usr/lib/selenium/selenium-server-standalone-2.6.0.jar -role hub
What is the expected output?
The grid hub should start normally.
What do you see instead?
17-Sep-11 12:21:35 org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
Exception in thread "main" java.lang.IllegalStateException: Failure initializing default
SSL context
at org.apache.http.conn.ssl.SSLSocketFactory.createDefaultSSLContext(SSLSocketFactory.java:211)
at org.apache.http.conn.ssl.SSLSocketFactory.<init>(SSLSocketFactory.java:333)
at org.apache.http.conn.ssl.SSLSocketFactory.getSocketFactory(SSLSocketFactory.java:165)
at org.openqa.selenium.remote.internal.HttpClientFactory.getClientConnectionManager(HttpClientFactory.java:55)
at org.openqa.selenium.remote.internal.HttpClientFactory.<init>(HttpClientFactory.java:44)
at org.openqa.grid.internal.Registry.<init>(Registry.java:84)
at org.openqa.grid.internal.Registry.newInstance(Registry.java:94)
at org.openqa.grid.web.Hub.<init>(Hub.java:97)
at org.openqa.grid.selenium.GridLauncher.main(GridLauncher.java:47)
Caused by: java.lang.IllegalStateException
at gnu.javax.net.ssl.provider.X509KeyManagerFactory.engineGetKeyManagers(libgcj.so.90)
at javax.net.ssl.KeyManagerFactory.getKeyManagers(libgcj.so.90)
at org.apache.http.conn.ssl.SSLSocketFactory.createSSLContext(SSLSocketFactory.java:187)
at org.apache.http.conn.ssl.SSLSocketFactory.createDefaultSSLContext(SSLSocketFactory.java:209)
...8 more
Selenium version: 2.6
OS: Debian 5.0.8
It seems that since the refactoring of DefaultHttpClient (http://code.google.com/p/selenium/source/detail?r=13680),
the error described above is raised. The same command line with Selenium 2.4 works
perfectly. I've made sure no other application was using the 443 SSL port and even
disabled the firewall. Maybe some more configuration is needed here (e.g. with the
'javax.net.ssl.keyStore' properties)?
Reported by simpleentrepreneur on 2011-09-17 10:31:11
The text was updated successfully, but these errors were encountered:
Originally reported on Google Code with ID 2483
Reported by
simpleentrepreneur
on 2011-09-17 10:31:11The text was updated successfully, but these errors were encountered: