I have a JBoss instance running and was started through the Jenkins startup command in JBoss plugin. After my tests have run I would like to shutdown the JBoss server. However at this stage Jenkins informs me
SHUTDOWN: Checking if server is running (max 20 seconds)...
SHUTDOWN: JBoss AS is not working.
I verified after the run that JBoss indeed is still running. Any ideas what to do to fix this?
Problem solved, I had the wrong JNDI port Jenkins JBoss settings.
Related
I was able to install and run jenkins on my linux subsystem in Windows 10.
It listens on 8082.
But unfortunately, for an unknown reason, it hangs up infinitely after a few minutes (or to be precise after a I've made a change in a job config and execute a build).
Then, I checked in the terminal:
root#jup1t3r /h/navds# service jenkins status
Correct java version found
2 instances of jenkins are running at the moment
but the pidfile /var/run/jenkins/jenkins.pid is missing
root#jup1t3r /h/navds# service jenkins stop
Correct java version found
* Stopping Jenkins Automation Server jenkins
...done.
root#jup1t3r /h/navds# service jenkins status
Correct java version found
2 instances of jenkins are running at the moment
but the pidfile /var/run/jenkins/jenkins.pid is missing
So there is no way to stop Jenkins. How can I restart it ?
We've been configuring an automated deployment using WebSphere Deployer Plugin v 1.3.4 for IBM WAS 8.5.
We have finished all the pipeline and checked the conecction to SOAP, all works right, but we have one last problem, jenkins throws this failure:
Jenkins Console Output
Generating EAR For Artifact: xxxxxxxxxx
Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact 'xxxxxxxxxx' is installed: ADMA0089E: The AppManagement MBean is not found.
We have researched a lot, but we can determine which is the problem?
Note: We configure the Generic JVM arguments with the IBM suport, these are the arguments we added:
Generic JVM arguments
-Dcom.ibm.team.server.monitoring.mbean.server=WebSphere
-Djavax.management.builder.initial=
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=10033
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Check WebSphere Connectivity Port setting in Jenkins, it should be SOAP port of Deployment Manager(default: 8879), not SOAP port of Websphere Application Server.
I'm running Jenkins 2.14 on Win 10.
I have started it as a Windows Service but now it cannot be stopped. When I go to Windows Services, it is showing as running but it cannot be stopped from the context menu.
Running net start jenkins / net stop jenkins displays the following:
Running sc queryex jenkins gives the following:
hitting localhost:8080 shows Jenkins is up but when I select 'Shutdown' from the webpage, it never shuts down!
Confused - anyone shed any light?
now working in latest Jenkins 2.14
I am using Ant to start/stop our JBoss server in Jenkins. The JBoss server starts fine in Jenkins, but the build never finishes even though the server has started. Is it possible to define in Ant or in Jenkins a way to overcome this? I.e. is it possible in Jenkins to overcome this, or is it possible in Ant to somehow start the server "in background" so that when Jenkins has executed the Ant task it immediately goes to next step in the build (I can manually define a sleep in Jenkins to wait for the server to start)?
Instead of using ant, you could explore JBoss Management Plugin
I am instrumenting Selenium tests that run against an application in a JBoss server. Many documentations mention that the Jacoco agent should be added as a parameter to the JVM. However, they do not state whether they mean the JVM where the Selenium tests are running or the JVM where the JBoss app server is running. They are totally different machines. So, is the Jacoco Agent added to:
1. the app server JVM upon start
2. or the JVM where Selenium tests are run?
Thanks.
I've never tried to use JaCoCo with Selenium tests, but obviously the agent should somehow be attached the JVM that runs the compiled sources of your application so that it can intrument your code at runtime (therefore, this is on server side).