Getting error in integrating jmeter with spring mvc - spring-mvc

I am trying to integrate jmeter with spring mvc. I have captured all the request using blazemeter and converted in .jmx file. I have placed this jmx file in test/jmeter folder. When I try to install, I am getting following error.
Executing test: Dagwidouthtml.jmx INFO 2016-07-06 14:10:59.229 [jmeter.e] (): Listeners will be started after enabling running version INFO 2016-07-06 14:10:59.230 [jmeter.e] (): To revert to the earlier behaviour, define jmeterengine.startlistenerslater=false [info] Completed Test: Dagwidouthtml.jmx [info] [info] Building JMeter Report(s)... [info] [info] Raw results: /home/trina/git/framework_loadTest/target/jmeter/report/Dagwidouthtml-160706.jtl [info] Test report: /home/trina/git/framework_loadTest/target/jmeter/report/Dagwidouthtml-160706.jtl-report.html [INFO] [INFO] Test Results: [INFO] [INFO] Tests Run: 1, Failures: 6, Errors: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 46.269 s [INFO] Finished at: 2016-07-06T14:11:10-04:00 [INFO] Final Memory: 44M/481M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.lazerycode.jmeter:jmeter-maven-plugin:1.4.1:jmeter (jmeter-tests) on project framework: There were test failures. See the jmeter logs for details. -> [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

So why you're posting Maven output here while it states the following:
There were test failures. See the jmeter logs for details
The log file is usually located at target/jmeter/logs/${yourscript}.log
Inspect the log file and if you won't be able to figure out the problem yourself.
The possible reason (apart from misconfiguration) I can think of is that jmeter-maven-plugin still depends on JMeter 2.13 so if you're trying to use features, introduced in JMeter 3.0 in your script - the failures are absolutely expected.
Also see documentation on JMeter Maven Plugin on Github - it is the most comprehensive source.

Related

pact- Contract Testing- The PACT file is not getting picked up for the execution

Initially started to analyze PACT by downloading the project from github location. In the existing project i have included my code for a GET request services.groupkt.com/country/get/iso2code/IN.
I was able to generate the PACT file but when i try to verify from the producer end i get the below message
D:\microservices-pact-maven-master\microservices-pact-consumer>mvn au.com.dius:p
act-jvm-provider-maven_2.11:verify
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building microservices-pact-consumer 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- pact-jvm-provider-maven_2.11:3.2.2:verify (default-cli) # microservic
es-pact-consumer ---
Loading pact files for provider Foo_Provider from D:\microservices-pact-maven-ma
ster\microservices-pact-consumer\target\pacts
Skipping D:\microservices-pact-maven-master\microservices-pact-consumer\target\p
**acts\Country_Consumer-Country_Provider.json as the provider names don't match pr
ovider.name: Foo_Provider vs pactJson.provider.name: Country_Provider
Found 1 pact files**
Verifying a pact between Foo_Consumer and Foo_Provider
[Using file D:\microservices-pact-maven-master\microservices-pact-consumer\tar
get\pacts\Foo_Consumer-Foo_Provider.json]
a request for Foos
returns a response which
has status code 200 (OK)
includes headers
Could someone help me fix this issue.
Thanks in advance
Sushma
This could be an issue with the provider name mentioned in the consumer test where the PACT is getting created. I think your code is having the below values in your consumer pact class.
#Pact(provider = "Foo_provider", consumer = "Foo_consumer")
Please change the provider and consumer names as per your requirement. Run the consumer test again and then run the provider test.

Server access Error while building Apache Spark 0.8.0

UPDATE : No idea how I ended up solving it, but it ended up working with 0.8.0. I think I just got the sources from an other repository which worked this time.
While executing sbt/sbt assembly to build Spark on my machine (I'm currently running Ubuntu on VirtualBox, but that shouldn't be the issue), I'm getting the following error:
[error] Server access Error: Connection timed out url=https://repository.cloudera.com/artifactory/cloudera-repos/org/eclipse/jetty/jetty-parent/20/jetty-parent-20.pom
It seems the above URL isn't working, and accessing it manually, even on other machines, doesn't work. Any ideas to get the file nonetheless ?
Here's the full console log if that helps somehow.
ulysse#ulysse-VirtualBox:~/Downloads/spark-0.8.0-incubating$ sbt/sbt assembly
[info] Loading project definition from /home/ulysse/Downloads/spark-0.8.0-incubating/project/project
Cloning into '/home/ulysse/.sbt/staging/90b1b0889ba1299e38f2'...
[info] Loading project definition from /home/ulysse/Downloads/spark-0.8.0-incubating/project
[info] Updating {git://github.com/ijuma/junit_xml_listener.git#fe434773255b451a38e8d889536ebc260f4225ce}default-052ce0...
[info] Resolving org.scala-sbt#precompiled-2_10_1;0.12.4 ...
[info] Done updating.
[info] Updating {file:/home/ulysse/Downloads/spark-0.8.0-incubating/project/}plugins...
[info] Resolving org.scala-sbt#precompiled-2_10_1;0.12.4 ...
[info] downloading http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases/com.eed3si9n/sbt-assembly/scala_2.9.2/sbt_0.12/0.9.1/jars/sbt-assembly.jar ...
[info] [SUCCESSFUL ] com.eed3si9n#sbt-assembly;0.9.1!sbt-assembly.jar (4422ms)
[info] downloading http://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbteclipse/sbteclipse-plugin/scala_2.9.2/sbt_0.12/2.2.0/jars/sbteclipse-plugin.jar ...
[info] [SUCCESSFUL ] com.typesafe.sbteclipse#sbteclipse-plugin;2.2.0!sbteclipse-plugin.jar (2195ms)
[info] downloading http://repo1.maven.org/maven2/com/github/mpeltonen/sbt-idea_2.9.2_0.12/1.5.1/sbt-idea-1.5.1.jar ...
[info] [SUCCESSFUL ] com.github.mpeltonen#sbt-idea;1.5.1!sbt-idea.jar (4589ms)
[info] downloading http://repo1.maven.org/maven2/net/virtual-void/sbt-dependency-graph_2.9.2_0.12/0.7.3/sbt-dependency-graph-0.7.3.jar ...
[info] [SUCCESSFUL ] net.virtual-void#sbt-dependency-graph;0.7.3!sbt-dependency-graph.jar (2009ms)
[info] downloading http://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbteclipse/sbteclipse-core/scala_2.9.2/sbt_0.12/2.2.0/jars/sbteclipse-core.jar ...
[info] [SUCCESSFUL ] com.typesafe.sbteclipse#sbteclipse-core;2.2.0!sbteclipse-core.jar (5483ms)
[info] downloading http://repo1.maven.org/maven2/org/scalaz/scalaz-core_2.9.2/6.0.4/scalaz-core_2.9.2-6.0.4.jar ...
[info] [SUCCESSFUL ] org.scalaz#scalaz-core_2.9.2;6.0.4!scalaz-core_2.9.2.jar (28459ms)
[info] downloading http://repo.typesafe.com/typesafe/releases/commons-io/commons-io/2.0.1/commons-io-2.0.1.jar ...
[info] [SUCCESSFUL ] commons-io#commons-io;2.0.1!commons-io.jar (1796ms)
[info] downloading http://repo1.maven.org/maven2/com/github/mdr/ascii-graphs_2.9.2/0.0.2/ascii-graphs_2.9.2-0.0.2.jar ...
[info] [SUCCESSFUL ] com.github.mdr#ascii-graphs_2.9.2;0.0.2!ascii-graphs_2.9.2.jar (2180ms)
[info] Done updating.
[info] Compiling 1 Scala source to /home/ulysse/.sbt/staging/90b1b0889ba1299e38f2/target/scala-2.9.2/sbt-0.12/classes...
[info] Compiling 1 Scala source to /home/ulysse/Downloads/spark-0.8.0-incubating/project/target/scala-2.9.2/sbt-0.12/classes...
[info] Set current project to root (in build file:/home/ulysse/Downloads/spark-0.8.0-incubating/)
Getting Scala 2.9.3 ...
downloading http://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.9.3/scala-compiler-2.9.3.jar ...
[SUCCESSFUL ] org.scala-lang#scala-compiler;2.9.3!scala-compiler.jar (64928ms)
downloading http://repo1.maven.org/maven2/org/scala-lang/scala-library/2.9.3/scala-library-2.9.3.jar ...
[SUCCESSFUL ] org.scala-lang#scala-library;2.9.3!scala-library.jar (48661ms)
downloading http://repo1.maven.org/maven2/org/scala-lang/jline/2.9.3/jline-2.9.3.jar ...
[SUCCESSFUL ] org.scala-lang#jline;2.9.3!jline.jar (1021ms)
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
4 artifacts copied, 0 already retrieved (20346kB/242ms)
[info] Updating {file:/home/ulysse/Downloads/spark-0.8.0-incubating/}core...
[info] Resolving org.eclipse.jetty#jetty-server;7.6.8.v20121106 ...
[error] Server access Error: Connection timed out url=https://repository.cloudera.com/artifactory/cloudera-repos/org/eclipse/jetty/jetty-server/7.6.8.v20121106/jetty-server-7.6.8.v20121106.pom
[info] Resolving org.eclipse.jetty#jetty-project;7.6.8.v20121106 ...
[error] Server access Error: Connection timed out url=https://repository.cloudera.com/artifactory/cloudera-repos/org/eclipse/jetty/jetty-project/7.6.8.v20121106/jetty-project-7.6.8.v20121106.pom
[info] Resolving org.eclipse.jetty#jetty-parent;20 ...
[error] Server access Error: Connection timed out url=https://repository.cloudera.com/artifactory/cloudera-repos/org/eclipse/jetty/jetty-parent/20/jetty-parent-20.pom
All of them seem to be available from Maven Central:
http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-server/7.6.8.v20121106/
http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-project/7.6.8.v20121106/
http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-parent/20/
Maybe by creating a bogus project using those dependencies, sbt will pull them from Maven Central and Ivy might cache them.
I also got this same error. Download the new version from this link and try again
http://d3kbcqa49mib13.cloudfront.net/spark-0.9.0-incubating.tgz
It took around 2 hour for me. If it fails, delete that folder and extract it again

issue when building NPanday Building a web application

[UPDATE]
the clean goal runs smoothely all over the projects of the solution, the problem now while running the compile goal, below the error message:
[INFO] Total time: 19.427s
[INFO] Finished at: Fri Jun 29 11:46:28 WEST 2012
[INFO] Final Memory: 15M/306M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.npanday.plugins:maven-aspx-plugin:1.4.0-incubating:compile (default-compile) on project B3GMcsInterface: NPANDAY-900-006: Unable to Compile: Language = ASP, Vendor = null, ArtifactType = asp, Source Directory = C:\Users\CASA-WS001\Desktop\Gateway\ProjectName: NPANDAY-040-001: Could not execute: Command = cmd.exe /X /C "aspnet_compiler -v " /MyArtifactId" -p C:\Users\CASA-W~1\AppData\Local\Temp\maven-aspx-plugin-3088047295012139775\src -u -f C:\Users\CASA-W~1\AppData\Local\Temp\maven-aspx-plugin-3088047295012139775\dest -nologo -fixednames", Result = 1 -> [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
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :B3GMcsInterface
NPanday Execution Failed!, with exit code: 1
[END OF UPDATE]
i'm trying to make the build of simple web application using NPanday, i am using the incubating 1.4.0 plugin for VS2010, i have successfully built C# Console or Libraries Projects using maven, but when i tried to clean a web application i encounter this kind of error
Below is the error output.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.628s
[INFO] Finished at: Tue Jun 26 17:53:56 WET 2012
[INFO] Final Memory: 6M/16M
[INFO] ------------------------------------------------------------------------
[ERROR] Error resolving version for plugin 'npanday.plugin:maven-aspx-plugin' from the repositories [local (C:\Users\user1.m2\repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository -> [Help1]
[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/PluginVersionResolutionException
any help is appreciated.
Thank You.
The problem is the "npanday.plugin" in "npanday.plugin:maven-aspx-plugin"... It must be wrongly stated in one of the life cycles.
Things have moved to "org.apache.npanday.plugins": http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22maven-aspx-plugin%22
Try using 1.5.0-SNAPSHOT from the following repository. It contains a mass of improvements! I'm using it in production.
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>false</enabled>
</releases>
<id>npanday.snapshots</id>
<name>NPanday Snapshot Repository</name>
<url>http://vmbuild.apache.org/archiva/repository/npanday-snapshots</url>
</pluginRepository>
</pluginRepositories>
I think you have to use a repository manager and define a supplemental repository which contains the given dependencies / plugins.
Error is related plugins order in pom.xml:
If maven-compile-plugin is before maven-aspx-plugin, you get the error.
But if the order is maven-aspx-plugin and then maven-compile-plugin, mvn compile works
Snip of the correct pom.xml:
....
<plugins>
<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>maven-aspx-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<frameworkVersion>4.0</frameworkVersion>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>maven-compile-plugin</artifactId>
<version>1.4.0-incubating</version>
<extensions>true</extensions>
....

Error using flashplayer in jenkins when running maven-release-plugin. Works when using mvn test

I have a maven 2 job configured in Jenkins, and under the Build I use
clean test release:prepare ...
in the goals options. Jenkins runs these goals sequenctiallay, and when test runs, it prints (and works nice):
[WARNING] [LAUNCHER] Using regular flashplayer tests
But when it tries to run prepare I get,
[INFO] [WARNING] [LAUNCHER] Using xvfb-run to launch headless tests
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Failed to launch Flash Player. Probably java was not able to find flashplayer.
[INFO] Make sure flashplayer is available on PATH
[INFO] or use -DflashPlayer.command=${flashplayer executable}
[INFO] Read more at: https://docs.sonatype.org/display/FLEXMOJOS/Running+unit+tests
So the same jobs, same jenkins, same job configuration, how can I make it work so that prepare also works like the clean goal?
I have also tried what the error suggest, that is, putting:
-Dflex.flashPlayer.command=/opt/player_10/flashplayer", "-DflashPlayer.command=/opt/player_10/flashplayer

An error occurred because there is no graphics environment available

I am getting below error when I try to use hudson and maven, Any idea how to resolve?
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error occurred because there is no graphics environment available. Please set the headless-server setting in the Flex configuration file to true.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.InternalError: An error occurred because there is no graphics environment available.
Thanks
sharp
Under <compiler> tag in flex-config.xml add
<headless-server>true</headless-server>

Resources