Contributions
Re: Running LoadUI from command line CentOS not working
Hi Mikael, You are correct. What I did is that I installed an Xvfb Jenkins extension: https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin. Then part of my Jenkins project steps, I had one step that starts Xvfb. Build Environment Start Xvfb before the build, and shut it down after. After that, I added an "Execute Shell" step where I exported the variables. export DISPLAY=:1.0 export GDFONTPATH=/opt/SmartBear/LoadUI-2.7.0/jre/lib/fonts Then I invoked LoadUI and It run okay. Now, I have only one last question, hopefully I have been trying to generate the report and then possibly export it to a different machine where I can look at the results but I had no luck. There were no errors but the report is not being generated. Is that because we are doing a workaround to get LoadUI to work which leads to loosing the possibility to generate a PDF report? Here is the command I am using: ./loadUI-cmd.sh -p /PROJECT_PATH -L 300:0:0 -r /home/ -F PDF Again Thanks a lot and I hope that other LoadUI users benefit from this post. Pat10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0CommentsRe: Running LoadUI from command line CentOS not working
Hi Mikael, I have already done that. But it seems it is not working. It is still throwing errors: Can't connect to X11 window server using ':99.0' as the value of the DISPLAY variable However, I might have found a solution. I will post it once it is confirmed. It could help other LoadUI users integrate their load tests with Jenkins. In the meantime, if you have other suggestions/solutions, please post them here. I will keep you posted. Thanks again, Pat10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.8KViews0likes0CommentsRe: Running LoadUI from command line CentOS not working
Hi Mikael, Again thanks for the tips of last time. That resolved the issue for me when I run LoadUI manually from command line on CentOS. Now, I am trying to automate my project using Jenkins and Ant. I wrote my build xml script and I am pretty sure I correctly invoked LoadUI. But to check, here is how I did it: <target name="loadUI" description="Run LoadUI Project" <exec dir="." executable="/opt/SmartBear/LoadUI-2.7.0/loadUI-cmd.sh"> <arg value="-p /project/path" /> <arg value="-L 300:0:0" /> </exec> </target> When I start my project from Jenkins (Web Interface), I get the following error: [exec] Exception in thread "AWT-EventQueue-0" java.awt.HeadlessException: [exec] No X11 DISPLAY variable was set, but this program performed an operation which requires it. [exec] at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:173) [exec] at java.awt.Window.<init>(Window.java:477) [exec] at java.awt.Frame.<init>(Frame.java:419) [exec] at javax.swing.JFrame.<init>(JFrame.java:218) [exec] at com.javafx.main.Main$1.run(Main.java:648) [exec] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226) [exec] at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:676) [exec] at java.awt.EventQueue.access$400(EventQueue.java:96) [exec] at java.awt.EventQueue$2.run(EventQueue.java:637) [exec] at java.awt.EventQueue$2.run(EventQueue.java:635) [exec] at java.security.AccessController.doPrivileged(Native Method) [exec] at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:108) [exec] at java.awt.EventQueue.dispatchEvent(EventQueue.java:646) [exec] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275) [exec] at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200) [exec] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190) [exec] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185) [exec] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177) [exec] at java.awt.EventDispatchThread.run(EventDispatchThread.java:138) It seems to be the same issue as before, do you have any idea or workaround that solves it? As I said earlier, if I run the project from command line (manually), everything works fine. Only when I run it from Jenkins, it throws the error. I will appreciate it so much if you can provide me with some feedback. Best Regards, Pat.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.8KViews0likes0CommentsRe: Running LoadUI from command line CentOS not working
Hi Mikael, It seems that everything worked fine. I followed the instructions provided in the link and LoadUI started successfully from command line. (I haven't done any further testing yet but as far as I see , LoadUI worked on my headless server) You rock Thanks for the support, ps: I hope this fix helps other LoadUI users. Pat10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.8KViews0likes0CommentsRe: Running LoadUI from command line CentOS not working
Hi Mikael, Thank you for your response. I followed the steps you asked me to do and here is the output I got after running fc-cache -v : /usr/share/fonts: caching, new cache contents: 8 fonts, 0 dirs /usr/share/X11/fonts/Type1: skipping, existing cache is valid: 13 fonts, 0 dirs /usr/share/X11/fonts/TTF: skipping, no such directory /usr/local/share/fonts: skipping, no such directory /root/.fonts: caching, new cache contents: 8 fonts, 0 dirs /var/cache/fontconfig: cleaning cache directory /root/.fontconfig: not cleaning non-existent cache directory Then when I run LoadUI again from command line using the following: ./loadUI-cmd.sh -p /opt/SmartBear/LoadUI-2.7.0/samples/sample1.xml , I didn't see the behavior that I described previously (which is good). However, I got this error: Starting with arguments: [--cmd=true, --nofx=true, -nofx, -Dlog4j.configuration=log4j_headless.xml, -p, /opt/SmartBear/LoadUI-2.7.0/samples/sample1.xml] (<unknown>:14609): Gtk-WARNING **: cannot open display: I am not sure how to move forward after this step so would you like to provide me with further instructions if possible? Is there a way to just run the test without generating the report since it seems that the tools used to generate the report are causing the issue? Best Regards, Pat.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.8KViews0likes0CommentsRunning LoadUI from command line CentOS not working
Hi everyone, I just tried to run LoadUI from command line on CentOS (HEADLESS server) and it seems that it is not working properly. LoadUI starts but then nothing shows up. What it is strange is that I don't see any errors. I have attached a document showing the behavior. 1. Would like to provide some help on this (if there is any)? I have a feeling, this is happening because I am running it on a headless server. Is there a way to bypass the JavaFX2 package? 2. I noticed some other abnormal behavior, I tried to stop it from running using "Ctrl + C". It stops for 1 second but then it restarts back so I wasn't able to stop it at all and I had to reboot the entire box. (killing the processes didn't help either. in fact each time I kill a process another one pops up) .:::. .==:::::. .====:::::::. .======:::::::::. .========:::::::::::. .:=========:::::::::::::. .:::=========:::::::::::::::. :::::=========::::::::::::::::: :::::=========::::::::::::::::: ':::=========:::::::::::::::' ':======================' '===================' '===============' '===========' ':::::::' ':::' :: :: :: :: :::: :: :: :: :: :: :: :::: ::::: :::::: :: :: :: :: :: :: :: :: :: :: :: :: :: :::::: :::: ::: : :::::: ::::: :::: LoadUI 2.7.0 Starting with arguments: [--cmd=true, --nofx=true, -nofx, -Dlog4j.configuration=log4j_headless.xml] Jul 09, 2014 3:14:29 PM com.eviware.loadui.launcher.JavaFxStarter ensureFontsAvailableForJavaFX INFO: Preparing fonts for JavaFX2 Jul 09, 2014 3:14:31 PM com.eviware.loadui.launcher.JavaFxStarter ensureFontsAvailableForJavaFX INFO: Restarting JRE for changes to take effect.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.5KViews0likes11CommentsRunning LoadUI from command line Mac
Hi everyone, I just started testing LoadUI (open source) and I am working on running it from command line. I got to a point where I was able to run my project from command line however there were couple of errors that were thrown along the way. I am not what is wrong with this error? I also noticed that the number of requests sent isn't matching the expected number of requests based on the generator I am using in my tests. It is much more less. As a side note, when I run the project from GUI, the load is heavier (more requests have being sent). 1. So does the command line affect the load (i.e the number of requests generated per unit of time)? 2. Would like to checkout the errors and give me some insights on what is going on? I am not sure how those errors are critical to running the test from command line (because I was able to run the test even with these errors) but it would be better not to see them coming up. Here are some details about the project I have: I have a fixed rate generator (couple of them), each one of them is linked to a SoapUI Runner and each SoapUI runner is connected to two log tables (one for failures and one for success). Please find attached the errors I am getting.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0Comments