I installed serverAgent 2.2.3
When I run it in cmd I get this error.
enter image description here
I tried starting the startAgent. bat. It automatically closes.
Thanks for looking.
That's very weird because the error states that sl4j library cannot be found in CLASSPATH and ServerAgent doesn't use this library at all.
Try downloading it from Github and unpacking it somewhere else. Also if you have CLASSPATH environment variable set - try clearing/unsetting it.
set CLASSPATH= && startAgent.bat
More information: How to Monitor Your Server Health & Performance During a JMeter Load Test
Alternatively you can try downloading sl4j.jar and dropping it near ServerAgent.jar but it is not a part of normal ServerAgent installation procedure.
Related
For a few days I cannot open any JMX file in JMeter script. Even after click File->Recently Opened, JMeter opens this file but non of click action on this file doesn't work. I am using JMeter version 5.3.
What I've done:
tried to used another JMeter version (5.5)
unistalled and installed newest JDK version (17.0.4.1)
upgraded all MacOS upgraded
scanned my MACOS in order to find a viruses
opened another applications based on Java and try to open the file (f.e. Intelij)
Increased Heap from 256M to 512M
Killed all denudant processes
Opened the java logs
All these actions were unsuccessful. Slowly my ideas are ran-down. Any idea from you what else can I check?
Best regards.
I cannot reproduce your issue:
so most probably something is wrong with your Java/JMeter/OS/user/whatever.
You can try following troubleshooting steps:
Increase JMeter's logging verbosity to maximum and see whether there are any suspicious entries in jmeter.log file
Check your OS logs using Console application
Try switching to another Look and Feel via Options -> Look and Feel. If this doesn't work as well you can do it using command line i.e.
./jmeter.sh -Jjmeter.laf=CrossPlatform
Try running JMeter and providing the path to the .jmx script via -t command-line argument like:
./jmeter -t /path/to/test.jmx
I tried to set input file path as below. But getting error as
"WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.".
Can some one help me.
This is how I've configured:
cd D:\Automation\Jmeter_Param\apache-jmeter-4.0\apache-jmeter-4.0\bin\
set my_dataset=D:\Automation\Jmeter_Param\apache-jmeter-4.0\apache-jmeter-4.0\bin\Deactivate.csv
set my_txnset=D:\Automation\Jmeter_Param\apache-jmeter-4.0\apache-jmeter-4.0\bin\Deactivate\credentials_prod.csv
jmeter -n -t D:\Automation\Jmeter_Param\apache-jmeter-4.0\apache-jmeter-4.0\bin\Deactivate\Deactivate.jmx
Here my_dataset and my_txnset has been called out under Global and used.
As per JMeter release notes:
Note that under some windows systems you may have this WARNING:
java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0
x80000002. Windows RegCreateKeyEx(…) returned error code 5.
The fix is to run JMeter as Administrator, it will create the registry key for you, then you can restart JMeter as a normal user and you won't have the warning anymore.
So just run the command prompt as Administrator once and issue will go away.
Also be aware that according to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article you should always be using the latest version of JMeter so consider upgrading to JMeter 5.2.1 (or whatever is the latest stable version available at JMeter Downloads page) on next available opportunity
I'm working on the installation of Workload-Scheduler, which is done through IBM Installation Manager. I need to stop the installation manager for debugging purpose before the end of the installation. How can I do that?
Modify the log.properties of IM (Usually in C:\ProgramData\IBM\InstallationManager\logs) with the properties described below.
Open IM from command line using IBMIMc.exe and not IBMIM.exe, otherwise these options have no effect.
Sample of log.properties:
InstallOperation=DEBUG
InstallOperation/pause.after=install:com.ibm.tws.agent.windows..com.ibm.tws.agent.windows.deployagentwin64:zip:2
InstallOperation/pause.on_error=true
com.ibm.tws=DEBUG
This allow to block the installation after the unzip of the agent just before the execution of twsinst, so it is possible to modify the agent files on the fly and let the installation to go.
Another example to block the installation at the very beginning:
InstallOperation/pause.before=pre_install_configure:com.ibm.tws.tdwb.unix..com.ibm.tws.tdwb.unix.definehelpvariables:invoke
The option:
InstallOperation/pause.on_error=true
Cause the IM stop if there is an error. To restart IM you should hit enter in the command line window where you started IBMIMc.exe.
In the same window entries in the log are displayed in the command line window
I'm trying to install weblogic server on Centos 7 with following instruction of oracle about console mode. Everything will be fine till weblogic file 's extracting on my computer. I get this message about
display enviroment variable failed
I google it and found xming as solution. But is there any solution to install weblogic without xming.
You need to do a silent install as mentioned. You can find the documentation here.
Basically, you need two files:
A response file
Here, you will set some parameters like ORACLE_HOME, proxy information if needed and installation type, etc.
An oraInst.loc file
In this file, you need to do the following(from documentation):
Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Then, replace oui_install_group with the name of the group whose members have write permissions to this directory.
After doing all of this, you can run the command as follows;
java -jar distribution_name.jar -silent -responseFile file [-options] [()*]
I uploaded my own oraInst.loc and response files here for demonstration. I strongly suggest you to read the documentation though. Good luck.
Background
I am running a set of selenium tests using a Maven and Jenkins with Testng. I had them working fine headlessly up until a week ago. Jenkins sits on the server accessible with port 8080. The tests also run fine through eclipse.
Software Versions
I have read lots about Firefox being incomparable with selenium so here is a list of software and versions that I am using.
Firefox: 39
Maven: 3.3.3
Java: 1.7.0_79
Selenium: 2.46 & 2.47(currently 2.47)
Jenkins: 1.622
Xvnc: 1.3.9
ubuntu 14
Error
After I run the tests and the fail I check the console through Jenkins. The error I am getting makes me think it's a problem with Xvnc and firefox but I can't pin point it. I get a NotConnectedException. The firefox console error has changed a few times here is a list of different errors the console has shown me.
Error: cannot open display: :87
firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :46.
firefox: Fatal IO error 2 (No such file or directory) on X server :78.
Research
I've been on bugzilla but cant find a conclusive answer to the problem.
I've also looked around SO but found no fixes.
Conclution
From what I have gathered it is something to do with Xvnc, Could running
sudo apt-get update
make changes to how Xvnc operates? I have updated the packages some time last week but our testers didn't check Jenkins properly when adding new tests and as such I've wasted and entire day trying to pin point when and what the problem is.
Question
What would cause Jenkins to return errors like this, how can I fix them and how can I prevent something doing this again?
EDIT 1
The display variable seems to be the issue, upon typing the command
echo $DISPLAY
There is no response just an empty line.
EDIT 2
running the command
export DISPLAY=:0.10
no gives the result
:0.10
when I echo $DISPLAY
I think the DISPLAY varibale is not functioning as expected and hence firefox is unable to connect to it. To know more about the $DISPLAY refer this link https://askubuntu.com/questions/432255/what-is-display-environment-variable
Try to run this command on the slave node where the job runs, this should give you the required setting for the tests to connect and run.
nohup /usr/bin/Xvfb :2 –screen 0 1024x768x24 > /dev/null 2>&1 &