[JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile
by Dave Westerman (JIRA)
[ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.s... ]
Dave Westerman commented on ARQ-1961:
-------------------------------------
Gerhard,
I created a workaround where I took the source code, and changed it to use the deleteOnExit(), and also to not fail if it can't delete the archive (since the deleteOnExit does get rid of it). I have added that to our own local repository, and am using that to get past my problem.
I must be using more Arquillian functionality than my colleagues, because none of them have run into this problem (at least not yet).
I am getting another error which may or may not be related (since again, none of my colleagues are running into it). But I will post in the forum first, since it's not necessarily related.
> Exception while undeploying application in WebSphere Liberty Profile
> --------------------------------------------------------------------
>
> Key: ARQ-1961
> URL: https://issues.jboss.org/browse/ARQ-1961
> Project: Arquillian
> Issue Type: Bug
> Components: WebSphere Containers
> Environment: OS: Windows 7 Professional
> Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final
> org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2
> Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1
> WebSphere Liberty Profile: 8.5.5.4
> JUnit: 4.11
> Java: IBM Java 1.7 in 1.6 mode
> Reporter: Dave Westerman
> Assignee: Gerhard Poul
> Attachments: DaveWesterman_arquillian-enhanced-trace.zip
>
>
> I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service.
>
> All the tests run successfully. However, the JUnit test process always ends with an exception:
>
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application.
> at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184)
> ...
> Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory
> at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184)
> I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace:
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy
> FINER: ENTRY
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML
> FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML
> FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState
> FINER: ENTRY
> [AUDIT ] CWWKG0016I: Starting server configuration update.
> [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml
> [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml
> [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml
> [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml
> [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds.
> [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/
> [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful.
> [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test]
> [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping.
> [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully.
> [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully.
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState
> FINER: RETURN
> Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory
> FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps
> Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop
> FINER: ENTRY
> Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop
> FINER: RETURN
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (ARQ-1964) OperateOnDeployment not honored when using the JMX Protocol
by Sanne Grinovero (JIRA)
Sanne Grinovero created ARQ-1964:
------------------------------------
Summary: OperateOnDeployment not honored when using the JMX Protocol
Key: ARQ-1964
URL: https://issues.jboss.org/browse/ARQ-1964
Project: Arquillian
Issue Type: Bug
Affects Versions: 1.1.8.Final
Reporter: Sanne Grinovero
I was using protocol type {{jmx-as7}} to run tests on WildFly 9.0.0.Final, using
1.1.8.Final of Arquillian, and having the wildfly components aligned with the same versions I've found in WildFly 9's source code.
It seems like a random deployed is chosen, and all tests in the same class are run on that same deployment rather than on the ones I'm specifying with {{@OperateOnDeployment}}.
Switching to protocol {{Servlet 3.0}} seems to workaround the problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (ARQ-1963) Original exception lost when thrown from @Before-annotated method
by Christian Schulz (JIRA)
[ https://issues.jboss.org/browse/ARQ-1963?page=com.atlassian.jira.plugin.s... ]
Christian Schulz updated ARQ-1963:
----------------------------------
Steps to Reproduce: Throw an exception in the before method. (was: {code}
@RunWith(Arquillian.class)
public class ExceptionTest {
private Integer quantity;
@Deployment
public static Archive<?> createDeployment() {
return ShrinkWrap.create(WebArchive.class);
}
@Before
public void preparePersistenceTest() {
quantity = null;
throw new RuntimeException("test");
}
@Test
public void adjustSuccessful() {
assertTrue(quantity == null);
}
@After
public void clearData() throws Exception {
quantity.compareTo(1);
}
}
{code})
> Original exception lost when thrown from @Before-annotated method
> -----------------------------------------------------------------
>
> Key: ARQ-1963
> URL: https://issues.jboss.org/browse/ARQ-1963
> Project: Arquillian
> Issue Type: Bug
> Components: Base Implementation
> Reporter: Christian Schulz
>
> I have recognized that there seems to be an issue with JUnit and Arquillian.
> If there is an exception in @before-annotated method, it seems to be lost. There is no entry in the log neither the test will be aborted instantly.
> {code}
> @Before
> public void preparePersistenceTest() {
> throw new RuntimeException("test");
> {code}
> A NPE occurs in @after-annotated method. The @test-annotated method doesn't fail fast.
> Here the console output:
> {code}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.979 sec <<< FAILURE! - in RelocateTest
> relocateSuccessful(RelocateTest) Time elapsed: 0.24
> 1 sec <<< ERROR!
> java.lang.NullPointerException: null
> at RelocateTest.clearData(PackageRelocateTest.java:77)
> {code}
> *The issue*
> testFailure in ExpectedExceptionHolder is notified and overwrite an existing exception https://github.com/arquillian/arquillian-core/blob/e39433696861f115881808...
> This exception is used to create the testresult:
> https://github.com/arquillian/arquillian-core/blob/e39433696861f115881808...
> In my opinion there are two ways to handle this issue:
> - Don't overwrite an existing exception and discard the new exception
> - Change the TestResult class to hold multiple exceptions
> The first approach could be implemented very fast. I can't imagine a case when other exceptions are really needed. I would say other exceptions occur because the first exception occurred.
> https://github.com/arquillian/arquillian-core/issues/86
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARQ-1963) Original exception lost when thrown from @Before-annotated method
by Christian Schulz (JIRA)
Christian Schulz created ARQ-1963:
-------------------------------------
Summary: Original exception lost when thrown from @Before-annotated method
Key: ARQ-1963
URL: https://issues.jboss.org/browse/ARQ-1963
Project: Arquillian
Issue Type: Bug
Components: Base Implementation
Reporter: Christian Schulz
I have recognized that there seems to be an issue with JUnit and Arquillian.
If there is an exception in @before-annotated method, it seems to be lost. There is no entry in the log neither the test will be aborted instantly.
{code}
@Before
public void preparePersistenceTest() {
throw new RuntimeException("test");
{code}
A NPE occurs in @after-annotated method. The @test-annotated method doesn't fail fast.
Here the console output:
{code}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.979 sec <<< FAILURE! - in RelocateTest
relocateSuccessful(RelocateTest) Time elapsed: 0.24
1 sec <<< ERROR!
java.lang.NullPointerException: null
at RelocateTest.clearData(PackageRelocateTest.java:77)
{code}
*The issue*
testFailure in ExpectedExceptionHolder is notified and overwrite an existing exception https://github.com/arquillian/arquillian-core/blob/e39433696861f115881808...
This exception is used to create the testresult:
https://github.com/arquillian/arquillian-core/blob/e39433696861f115881808...
In my opinion there are two ways to handle this issue:
- Don't overwrite an existing exception and discard the new exception
- Change the TestResult class to hold multiple exceptions
The first approach could be implemented very fast. I can't imagine a case when other exceptions are really needed. I would say other exceptions occur because the first exception occurred.
https://github.com/arquillian/arquillian-core/issues/86
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARQ-838) Allow Arquillian Drone to handle Robotium
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-838?page=com.atlassian.jira.plugin.sy... ]
Karel Piwko closed ARQ-838.
---------------------------
Resolution: Rejected
Robotium could be handled by Droidium project instead. If you want to have it there, feel free to open new issue.
> Allow Arquillian Drone to handle Robotium
> -----------------------------------------
>
> Key: ARQ-838
> URL: https://issues.jboss.org/browse/ARQ-838
> Project: Arquillian
> Issue Type: Task
> Components: Extension - Drone
> Reporter: Karel Piwko
> Assignee: Aleksey Shilin
>
> Robotium is a Java based framework for testing Android applications using a high level API.
> Once the integration with Android integration tests is done, it would be convenient to have its support in Arquillian Drone.
> The key here is to grab current activity from Android context and provide a Solo object which could be injected into test itself.
> The usage might look similar to the following:
> {code}
> @RunWith(Arquillian.class)
> public class AndroidTest {
>
> @Test
> public void androidActivity(@AndroidActivity HelloAndroid helloAndroid, @Drone Solo solo) {
> solo.sendKey(Solo.MENU);
> solo.clickOnText("More");
> solo.clickOnText("Preferences");
> solo.clickOnText("Edit File Extensions");
> Assert.assertTrue(solo.searchText("rtf"));
> }
> }
> {code}
> Note that the above example does not reflect possible usage of Android/Robotium in class level, this a method-level proposal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months
[JBoss JIRA] (ARQ-1008) Can't use reusable remote driver with opera
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1008?page=com.atlassian.jira.plugin.s... ]
Karel Piwko closed ARQ-1008.
----------------------------
Resolution: Out of Date
Support for old Opera browser will not get any maintenance anymore.
> Can't use reusable remote driver with opera
> -------------------------------------------
>
> Key: ARQ-1008
> URL: https://issues.jboss.org/browse/ARQ-1008
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.CR2
> Reporter: Jan Papousek
> Assignee: Jan Papousek
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.303 sec <<< FAILURE!
> org.jboss.arquillian.drone.webdriver.example.WebDriverTestCase Time elapsed: 0 sec <<< ERROR!
> org.openqa.selenium.WebDriverException: Address already in use
> Command duration or timeout: 1.50 seconds
> Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 15:28:49'
> System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.43.8-1.fc15.x86_64', java.version: '1.7.0_04'
> Driver info: driver.version: RemoteWebDriver
> Session ID:
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:188)
> at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
> at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
> at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:155)
> at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:107)
> at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:115)
> at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:135)
> at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:162)
> at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:95)
> at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:49)
> at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:129)
> at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:43)
> at org.jboss.arquillian.drone.impl.DroneCreator.createWebTestBrowser(DroneCreator.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.drone.impl.DroneConfigurator.configureDrone(DroneConfigurator.java:116)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:344)
> at sun.nio.ch.Net.bind(Net.java:336)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
> at com.opera.core.systems.scope.stp.StpConnectionListener.start(StpConnectionListener.java:95)
> at com.opera.core.systems.scope.stp.StpConnectionListener.<init>(StpConnectionListener.java:58)
> at com.opera.core.systems.scope.stp.StpThread.<init>(StpThread.java:46)
> at com.opera.core.systems.ScopeServices.<init>(ScopeServices.java:112)
> at com.opera.core.systems.OperaDriver.createScopeServices(OperaDriver.java:251)
> at com.opera.core.systems.OperaDriver.init(OperaDriver.java:197)
> at com.opera.core.systems.OperaDriver.start(OperaDriver.java:186)
> at com.opera.core.systems.OperaDriver.<init>(OperaDriver.java:178)
> at com.opera.core.systems.OperaDriver.<init>(OperaDriver.java:160)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:57)
> at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:51)
> at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:196)
> at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:150)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 10 months