d6y / jchav

JChav is a way to see the change in performance of your web application over time, by running a benchmark test for each build you produce.
http://jchav.blogspot.com/
3 stars 0 forks source link

java.lang.InternalError: Can't connect to X11 window server when running jchav #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I have cruisecontrol, jmeter, and jchav installed on a headless linux box.
 When I was developing my ant scripts on a Linux machine, everything ran
fine, but now that it is deployed to our headless build machine, I am
getting the following error when it gets to the step of running jchav:

java.lang.InternalError: Can't connect to X11 window server using
'localhost:11.0' as the value of the DISPLAY variable.

I'm logged in over ssh.  I assume this is because jchav is using graphics
libraries on a headless machine.  (BTW, X11 and everything is installed.  I
can run remote xterms, etc.)

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
RHEL 5.0

Please provide any additional information below.

Are there instructions or workarounds for this issue?  Is there any
recommended ways of running or starting cruisecontrol so that this will not
be a problem?

Original issue reported on code.google.com by morttall...@gmail.com on 31 Aug 2007 at 1:34

GoogleCodeExporter commented 9 years ago
You need to tell the JDK that you do not have a graphics head. The simple way 
to do
this in java is to set the flag java.awt.headless to true.

In the current JChav docs/example you can do this by adding a parameter to the 
ant run :

 ant -f build-example.xml -Djava.awt.headless=true 

Original comment by paul.goulbourn on 22 Dec 2007 at 11:20

GoogleCodeExporter commented 9 years ago

Original comment by paul.goulbourn on 22 Dec 2007 at 11:30

GoogleCodeExporter commented 9 years ago
Test note: I was able to reproduce this problem on a headless RHEL machine only 
if I
explicitly set the DISPLAY variable. Unseting the DISPLAY variable may also 
resolve
this.  

Original comment by dalla...@gmail.com on 22 Dec 2007 at 12:56