I am getting this error while running selenium script in jenkins:
Building in workspace /home/jenkins_home/jobs/fe-integration-test/workspace
$ /usr/local/jdk1.6.0_34/bin/java -cp /home/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/usr/local/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /usr/local/apache-maven-3.0.4 /opt/wikiandsonartomcat/apache-tomcat-7.0.30/webapps/jenkins/WEB-INF/lib/remoting-2.16.jar /home/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 42127
<===[JENKINS REMOTING CAPACITY]===>channel started
Building single Maven modules is not implemented for Maven 3, yet!
Finished: ABORTED'
My server is CENT OS.
Can any one tell me how to get out of this error.
Today I got around this error by simply restarting Jenkins service (windows 7).
The root cause comes from Jenkins maven-plugin, so it should be fixed there first.
As of 2014-03-12 the code seems to have been improved.
Related
Problem:
I'm trying to install tensorflow-amd and one of the dependencies is bazel. On installation of bazel I get the following error message:
[miner-ms7a59 Downloads]# sudo pacman -S bazel
resolving dependencies...
looking for conflicting packages...
Packages (7) jdk11-openjdk-11.0.16.1.u1-2 jre11-openjdk-11.0.16.1.u1-2 jre11-openjdk-headless-11.0.16.1.u1-2 libnet-1:1.1.6-1 unzip-6.0-19 zip-3.0-10
bazel-5.2.0-1
Total Installed Size: 382.41 MiB
:: Proceed with installation? [Y/n]
(7/7) checking keys in keyring [#######################################################] 100%
(7/7) checking package integrity [#######################################################] 100%
(7/7) loading package files [#######################################################] 100%
(7/7) checking for file conflicts [#######################################################] 100%
(7/7) checking available disk space [#######################################################] 100%
:: Processing package changes...
(1/7) installing libnet [#######################################################] 100%
(2/7) installing jre11-openjdk-headless [#######################################################] 100%
Optional dependencies for jre11-openjdk-headless
java-rhino: for some JavaScript support
(3/7) installing jre11-openjdk [#######################################################] 100%
when you use a non-reparenting window manager,
set _JAVA_AWT_WM_NONREPARENTING=1 in /etc/profile.d/jre.sh
Optional dependencies for jre11-openjdk
alsa-lib: for basic sound support [installed]
gtk2: for the Gtk+ 2 look and feel - desktop usage [installed]
gtk3: for the Gtk+ 3 look and feel - desktop usage [installed]
(4/7) installing jdk11-openjdk [#######################################################] 100%
(5/7) installing zip [#######################################################] 100%
(6/7) installing unzip [#######################################################] 100%
(7/7) installing bazel [#######################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Refreshing PackageKit...
(3/4) Updating icon theme caches...
(4/4) Updating the desktop file MIME type cache...
[miner-ms7a59 Downloads]# bazel --version
bazel 5.2.0
[miner-ms7a59 Downloads]# bazel
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a WORKSPACE file).
Extracting Bazel installation...
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.ExceptionInInitializerError
at com.google.devtools.build.lib.skyframe.SkyframeExecutor.<clinit>(SkyframeExecutor.java:373)
at com.google.devtools.build.lib.skyframe.BazelSkyframeExecutorConstants.newBazelSkyframeExecutorBuilder(BazelSkyframeExecutorConstants.java:63)
at com.google.devtools.build.lib.skyframe.SequencedSkyframeExecutorFactory.create(SequencedSkyframeExecutorFactory.java:43)
at com.google.devtools.build.lib.runtime.WorkspaceBuilder.build(WorkspaceBuilder.java:73)
at com.google.devtools.build.lib.runtime.BlazeRuntime.initWorkspace(BlazeRuntime.java:265)
at com.google.devtools.build.lib.runtime.BlazeRuntime.newRuntime(BlazeRuntime.java:1316)
at com.google.devtools.build.lib.runtime.BlazeRuntime.batchMain(BlazeRuntime.java:925)
at com.google.devtools.build.lib.runtime.BlazeRuntime.main(BlazeRuntime.java:762)
at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:87)
Caused by: java.lang.NullPointerException
at java.base/jdk.internal.platform.cgroupv2.CgroupV2Subsystem.getInstance(CgroupV2Subsystem.java:81)
at java.base/jdk.internal.platform.CgroupSubsystemFactory.create(CgroupSubsystemFactory.java:113)
at java.base/jdk.internal.platform.CgroupMetrics.getInstance(CgroupMetrics.java:167)
at java.base/jdk.internal.platform.SystemMetrics.instance(SystemMetrics.java:29)
at java.base/jdk.internal.platform.Metrics.systemMetrics(Metrics.java:58)
at java.base/jdk.internal.platform.Container.metrics(Container.java:43)
at jdk.management/com.sun.management.internal.OperatingSystemImpl.<init>(OperatingSystemImpl.java:182)
at jdk.management/com.sun.management.internal.PlatformMBeanProviderImpl.getOperatingSystemMXBean(PlatformMBeanProviderImpl.java:281)
at jdk.management/com.sun.management.internal.PlatformMBeanProviderImpl$3.nameToMBeanMap(PlatformMBeanProviderImpl.java:198)
at java.management/sun.management.spi.PlatformMBeanProvider$PlatformComponent.getMBeans(PlatformMBeanProvider.java:195)
at java.management/java.lang.management.ManagementFactory.getPlatformMXBean(ManagementFactory.java:686)
at java.management/java.lang.management.ManagementFactory.getOperatingSystemMXBean(ManagementFactory.java:388)
at com.google.devtools.build.lib.util.ResourceUsage.<clinit>(ResourceUsage.java:42)
... 9 more
[miner-ms7a59 Downloads]#
Building bazel with the git repository with yay didn't really help much either, since it gave the same error message in the middle of the build. A lot of other stackoverflow questions trail off into either the java version or the linux version, even though the java version I'm running right now is openjdk 11.0.16.1 2022-08-12 and I dont have any other jdk installed other than jdk11-openjdk 11.0.16.1.u1-2, jre11-openjdk 11.0.16.1.u1-2, jre11-openjdk-headless 11.0.16.1.u1-2 (given by pacman -Q | grep jdk)
Hi everyone I'm executing a job on Talend 6.3.1 on the commandline using this command :
executeJob job_name -i /etc/alternatives/jre_1.8.0_openjdk/bin/java -jc DEV
and I always get the following error.
Error Line: 8113 Detail Message: com.jcraft cannot be resolved to a
type
The job is using an SFTP component that calls the jsch-0.1.53.jar, the jar is present in the job but for some reason it doesn't seem to find it. The commandline log shows :
!MESSAGE 2019-10-14 17:40:29,926 INFO
org.talend.commons.exception.CommonExceptionHandler - Missing jars:
jsch-0.1.53.jar
We also checked if the problem was the jdk version we're using but no results so far.
The job works perfectly fine when executed on the studio or even when built then executed on the server just not on the commandline.
Is it possible for you to publish the job to Nexus Repository, and then retrieve the job on TAC from Nexus ? This way, the job is only compiled once in the studio, you won't have to use the commandline (as the job is already compiled). It is simpler than resolving libraries issues with the commandline.
I am new to WebSphere Application Server.Getting this error in WAS Console while executing junit class (RunAs--> JUnit Test)
Running as Junit Test in Rational Application Developer
Actual Error Message is:
JVMJ9TI001E Agent library D:\Program Files\IBM\SDPShared\plugins\org.eclipse.tptp.platform.jvmti.runtime_4.7.0.v201110280852\agent_files\win_em64t\JPIBootLoader could not be opened (D:\Program Files\IBM\SDPShared\plugins\org.eclipse.tptp.platform.jvmti.runtime_4.7.0.v201110280852\agent_files\win_em64t\JPIBootLoader is not a valid Win32 application. )
JVMJ9VM015W Initialization error for library j9jvmti24(-3): JVMJ9VM009E J9VMDllMain failed .
Came Across this below links and tried but can't able to resolve"
link1-IBM
link2-IBM
I am using windows 10 64 bit, RAD 8.0.4 , WAS 7.0.23 ,Junit 4.12.
Help me to resolve this issue. Thanks in Advance.
Is the Junit running within the IDE's JVM? To check click on Run > Run Configurations, and look for the unit test you are trying to run. Then click on the JRE tab. It should show the Project Execution Environment.
Also, you're on a considerably old version of RAD and WAS. Any reason you can't upgrade?
I'm really new to maven and storm so I'm trying to follow the instructions in https://github.com/apache/storm/tree/master/examples/storm-starter. My current path is /home/luc/theTest/storm/examples/storm-starter. Inside the target folder there is a storm-starter-2.0.0-SNAPSHOT.jar file. I'm getting stuck when running
storm jar target/storm-starter-*.jar org.apache.storm.starter.ExclamationTopology -local
I get this error
ionTopology -local
Running: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -client -Ddaemon.name= -Dstorm.options= -Dstorm.home=/home/luc/stormTest/apache-storm-1.1.1 -Dstorm.log.dir=/home/luc/stormTest/apache-storm-1.1.1/logs -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib -Dstorm.conf.file= -cp /home/luc/stormTest/apache-storm-1.1.1/lib/servlet-api-2.5.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/slf4j-api-1.7.21.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/objenesis-2.1.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/kryo-3.0.3.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/log4j-core-2.8.2.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/log4j-over-slf4j-1.6.6.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/storm-core-1.1.1.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/log4j-slf4j-impl-2.8.2.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/minlog-1.3.0.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/log4j-api-2.8.2.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/clojure-1.7.0.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/ring-cors-0.1.5.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/asm-5.0.3.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/reflectasm-1.10.1.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/disruptor-3.3.2.jar:/home/luc/stormTest/apache-storm-1.1.1/lib/storm-rename-hack-1.1.1.jar:target/storm-starter-2.0.0-SNAPSHOT.jar:/home/luc/stormTest/apache-storm-1.1.1/conf:/home/luc/stormTest/apache-storm-1.1.1/bin -Dstorm.jar=target/storm-starter-2.0.0-SNAPSHOT.jar -Dstorm.dependency.jars= -Dstorm.dependency.artifacts={} org.apache.storm.starter.ExclamationTopology -local
Error: Could not find or load main class org.apache.storm.starter.ExclamationTopology
Am I doing something wrong? I'm also a bit confused on whether I have to run the nimbus and supervisor first. I tried with and without them and neither worked anyways. Been searching the web but nothing works. Not sure what else to try.
This is usually caused by inconsistent versions of storm-client and storm-starter. Try following these steps to get the example working.
download the latest release from http://storm.apache.org/downloads.html
in this example, we will use version 1.1.1
extract this to a folder, lets call it ${STORM_HOME}
cd into ${STORM_HOME}/examples/storm-starter
execute mvn package -DskipTests=true
this should build the storm-starter jar in target folder
${STORM_HOME}/examples/storm-starter/target/storm-starter-1.1.1.jar
run the example from ${STORM_HOME} directory:
./bin/storm jar examples/storm-starter/target/storm-starter-1.1.1.jar org.apache.storm.starter.ExclamationTopology
don't add the -local flag since it seems like the ExclamationTopology is only deployed in a LocalCluster if no args are passed. You can check the source code here: ${STORM_HOME}/examples/storm-starter/src/jvm/org/apache/storm/starter/ExclamationTopology.java
I'm a newbie in Grails Framework, I've downloaded Grails version 2.4.4 and set Path to it.
I create new application (like "hello world") but when run it with command (after cd application folder): grails run-app ,
cmd was stopped at this line : Configuring classpath.
Then I google, and try to use this way : setting "verbose" in BuildConfig.groovy file and it still like before with these errors :
| Error Resolve error obtaining dependencies: Failed to read artifact descriptor for org.slf4j:jcl-over-slf4j:jar:1.7.5
org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.slf4j:jcl-over-slf4j:jar:1.7.5
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:370)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:525)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:509)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:494)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363)
What can I do next?? and why it has these error, and what can I do for running this application.
P/s : Java version that I use is Java 1.6.0, OS: window 7.
Thank for any help.
This is a proxy issue, you can execute below commands:
grails add-proxy "client" "--host=yourHostName" "--port=8080" "--username=***" "--password='PASSWORD_GOES_HERE'"
grails set-proxy client
I believe the notation is incorrect for your dependency. You have:
org.slf4j:jcl-over-slf4j:jar:1.7.5
this includes a jar reference, which is unnecessary. Can you try:
org.slf4j:jcl-over-slf4j:1.7.5
Also, it looks like version 1.7.9 is available as of December 2014, if you want to use the latest.