When I run my Automation test script locally its working absolutely fine without any error message. But when I run on server, I can see that its working fine, but at the end, instead of Pass status, it shows test failure.
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 282.662 sec <<<
FAILURE!
allNumbersEditorsDraws(NumbersEditor.TestSuiteAdmin) Time elapsed: 0.047 sec <
<< FAILURE!
org.openqa.selenium.remote.SessionNotFoundException: Session ID is null. Using WebDriver after calling quit()?
Build info: version: '2.53.1', revision: 'a36b8b1cd5757287168e54b817830adce9b0158d', time: '2016-06-30 19:26:09'
System info: host: 'W-SL-DEVBUILD1', ip: '10.130.32.68', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_131'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:134)
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:82)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:644)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:363)
at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:500)
at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:355)
at NumbersEditor.LoginPage.loginAdmin(LoginPage.java:32)
at NumbersEditor.TestSuiteAdmin.allNumbersEditorsDraws(TestSuiteAdmin.java:18)
Results :
Failed tests: allNumbersEditorsDraws(NumbersEditor.TestSuiteAdmin): Session ID is null. Using WebDriver after calling quit()?(..)
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:50 min
[INFO] Finished at: 2017-06-26T10:41:18+01:00
[INFO] Final Memory: 13M/328M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
12.4:test (default-test) on project NumbersEditor: There are test failures.
[ERROR]
[ERROR] Please refer to C:\BuildAgent\work\f3b21200f1a5caf2\Automation\target\su
refire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
This is a common issue when you are doing UI test with Selenium on virtual machines.
When you run your tests, your session should be active. So, if you are connected in remote desktop on the VM, the current script is working, but, if you exit, the current session disapear.
In order to make it works, you should leave the current remote session with a script :
for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (
%windir%\System32\tscon.exe %%s /dest:console
)
Related
I updated all architecture (Java17, Maven3, Spring 2.7/core5.3...) and Vaadin 23, but I can only run in development mode. I can no longer run -Pproduction. Build failure :
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33.260 s
[INFO] Finished at: 2022-08-31T11:35:42-03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.vaadin:flow-maven-plugin:23.1.6:build-frontend (default) on project template-module-app: Could not execute build-frontend goal: Error occured during goal execution: Cannot invoke "java.lang.Class.isInterface()" because the return value of "org.reflections.Reflections.forClass(String, java.lang.ClassLoader[])" is nullPlease run Maven with the -e switch (or Gradle with the --stacktrace switch), to learn the full stack trace. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.vaadin:flow-maven-plugin:23.1.6:build-frontend (default) on project template-module-app: Could not execute build-frontend goal
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)
I've tried everything:
https://vaadin.com/docs/latest/tools/mpr/configuration/production-mode
https://vaadin.com/docs/latest/tools/ce/going-to-production
https://vaadin.com/docs/latest/production/troubleshooting
...
I recently started studying Vaadin. At the beginning I am using Vaadin 8 and have started a small Vaadin project in eclipse for practice purposes. I always started and opened this project via Jetty on my localhost:8080. That worked great for the first few days, but since yesterday
my localhost:8080 wants username and password at once and the application is no longer opening there.
The only difference is that the day before yesterday I installed an Oracle database (OracleXE 11 g) - could that have something to do with it?
Here is a snipppet if the error-message that I am getting:
Sep. 12, 2021 10:51:20 VORM. org.atmosphere.cpr.AtmosphereFramework addInterceptorToAllWrappers
INFORMATION: Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority BEFORE_DEFAULT
[INFO] Started o.e.j.m.p.JettyWebAppContext#60b616c8{/,file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/,AVAILABLE}{file:///C:/Repositories/ProgrammingCourses/Vaadin-and-Maven_Crash-Course/VaadinFirstSteps/src/main/webapp/}
[INFO] Jetty server exiting.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 42.520 s
[INFO] Finished at: 2021-09-12T10:51:20+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.3.9.v20160517:run (default-cli) on project VaadinFirstSteps: Failure: Address already in use: bind -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Anyone know how to get Vaadin up and running again? I am grateful fur any help,
Zrebna :)
"Failure: Address already in use: bind" means that you are trying to start web application server on localhost port 8080 while there is already web application server running and owning that port. Hence new one cannot be started.
You need to check you processes already running and kill the old one.
I'm following http://www.mulesoft.org/documentation... to create a connector to a SOAP Service via CXF Client Example. When I add the required maven dependency code in ,pom file and clean and run it(on mule studio)...I'm getting the following error :
Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.5.9:wsdl2java (default) on project sunsetriseconnector: javax/xml/ws/Action
The full stack trace looks like this :
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Sunset Sunrise Service 1.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> studio-maven-plugin:3.4.2:studio (default-cli) # sunsetriseconnector >>>
[INFO]
[INFO] --- mule-devkit-maven-plugin:3.4.0:attach-test-resources (default-attach-test-resources) # sunsetriseconnector ---
[INFO] Attaching test resource D:\MuleExamples\sunsetrise\src\main\app
[INFO]
[INFO] --- maven-enforcer-plugin:1.0-alpha-4:enforce (enforce-maven-version) # sunsetriseconnector ---
[INFO]
[INFO] --- mule-devkit-maven-plugin:3.4.0:generate-sources (default-generate-sources) # sunsetriseconnector ---
[INFO] Source directory: D:\MuleExamples\sunsetrise\target\generated-sources\mule added
[INFO] Resource directory: D:\MuleExamples\sunsetrise\target\generated-sources\mule added
[INFO] Sorting generator executing based on their dependencies...
[INFO] Searching for classes annotated with #Connector
[INFO] Validating sunsetriseConnector class
[INFO] Validating Multi-module consistency
[INFO] Adding registry bootstrap entry for org.tutorial.sunsetrise.agents.DefaultSplashScreenAgent as DefaultSplashScreenAgent
[INFO] Generating message processor as org.tutorial.sunsetrise.processors.MyProcessorMessageProcessor for method myProcessor in sunsetriseConnector
[INFO] Generating config element definition parser as org.tutorial.sunsetrise.config.sunsetriseConnectorConfigDefinitionParser for class sunsetriseConnector
[INFO] Generating bean definition parser as org.tutorial.sunsetrise.config.MyProcessorDefinitionParser for message processor org.tutorial.sunsetrise.processors.MyProcessorMessageProcessor
[INFO] Validating example for method: myProcessor
log4j:WARN No appenders could be found for logger (org.springframework.beans.factory.xml.PluggableSchemaResolver).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
[INFO]
[INFO] --- cxf-codegen-plugin:2.5.9:wsdl2java (default) # sunsetriseconnector ---
May 2, 2014 12:18:13 PM org.apache.cxf.xjc.bg.BooleanGetterPlugin run
INFO: Running boolean getter plugin.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.464s
[INFO] Finished at: Fri May 02 12:18:13 IST 2014
[INFO] Final Memory: 33M/62M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.5.9:wsdl2java (default) on project sunsetriseconnector: javax/xml/ws/Action -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I'm pretty new in mule and also in Apache cxf. Please help me.
Thanks.
I got the fix by adding jaxws-api-2.2.1.jar inside C:\Program Files (x86)\Java\jdk1.6.0_02\jre\lib\endorsed folder.
If you're using MuleStudio, which is built on Eclipse, you should import the JAR into your build path. See This SO answer
If you're using Mule ESB Standalone, you should drop the JAR into the MULE_HOME/apps/yourapp/lib directory if you need it on a per-app basis, or in the /MULE_HOME/lib/user
See the class loader documentation
Hello I am trying to install Hue on AWS EC2 instance.
Following below link.
https://github.com/cloudera/hue
While doing step make apps I am getting below error.
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message:
Detected JDK Version: 1.6.0-30 is not in the allowed range [1.7.0,1.7.1000].
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.717s
[INFO] Finished at: Sun Mar 09 13:18:59 EDT 2014
[INFO] Final Memory: 5M/25M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce (default) on project hue-parent: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
I have java version
java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Additional information can be provided. Thanks for your help.
You can also remove the JDK 7 check by editing:
vim maven/pom.xml
And replacing the '7' by '6':
<javaVersion>1.7</javaVersion>
<sourceJavaVersion>1.7</sourceJavaVersion>
<targetJavaVersion>1.7</targetJavaVersion>
(obviously you should it might be better to make sure Java 7 is the default if you plan to use 7)
It looks like you have another Java version in your system too. Based on what your installation says:
Detected JDK Version: 1.6.0-30
Make sure your JAVA_HOME variable points to the home of your Java 1.7 installation.
When i am trying to build wso2 api mgnt i got this error: Please help me
mvn clean install
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:22.482s
[INFO] Finished at: Wed Apr 24 15:02:05 IST 2013
[INFO] Final Memory: 19M/490M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.wso2.maven:carbon-p2-plugin:1.5:p2-profile-gen
(3-p2-profile-generation) on project am-p2-profile: P2 publisher return code was 13 -> [
First you have to build orbit then kernal and after that the platform. Have you done that order. If you get the same error can you paste full error log.
Thanks !