Hmmm... it really looks like a hang. The test runs to completion (I see the output FAILURES!!, and then:

[java] FAILURES!!!
[java] Xlib: unexpected async reply (sequence 0x11b)!
[java] Tests run: 110, Failures: 2, Errors: 0
[java] java.awt.headless=false
[java] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
[java] Headless? false
[java] Found class: sun.awt.X11GraphicsEnvironment

and it hangs. The command being run is:


/usr/local/lib/jdks/j2sdk1.4.2_02/jre/bin/java -Djava.awt.headless=false -classpath /home/jordi/load-test/Eclipse/jakarta-jmeter/lib/Tidy.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/avalon-excalibur-4.1.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/avalon-framework-4.1.4.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/commons-collections.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jakarta-oro-2.0.7.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jdom-b8.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/js.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/junit.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/logkit-1.2.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/soap.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/velocity-1.4-dev.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xalan.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xercesImpl.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xml-apis.jar
:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/htmlparser.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jorphan.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/bsf.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_core.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_components.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_functions.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_http.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_ftp.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_jdbc.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_java.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_ldap.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_tcp.jar org.apache.jorphan.test.AllTests ../lib/ext ./jmetertest.properties org.apache.jmeter.util.JMeterUtils

and two thread dumps taken a few seconds appart show the main thread stuck at the same point:

     [java] "main" prio=1 tid=0x08053788 nid=0x6ea2 runnable [bfffc000..bfffca78]
     [java]     at sun.awt.X11GraphicsEnvironment.getNativeFonts(Native Method)
     [java]     at 
sun.awt.X11GraphicsEnvironment.initNativeFonts(X11GraphicsEnvironment.java:529)
     [java]     at 
sun.awt.X11GraphicsEnvironment.registerFontPaths(X11GraphicsEnvironment.java:726)
     [java]     at 
sun.java2d.SunGraphicsEnvironment$1.run(SunGraphicsEnvironment.java:185)
     [java]     at java.security.AccessController.doPrivileged(Native Method)
     [java]     at 
sun.java2d.SunGraphicsEnvironment.<init>(SunGraphicsEnvironment.java:85)
     [java]     at 
sun.awt.X11GraphicsEnvironment.<init>(X11GraphicsEnvironment.java:163)
     [java]     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)
     [java]     at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     [java]     at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     [java]     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     [java]     at java.lang.Class.newInstance0(Class.java:308)
     [java]     at java.lang.Class.newInstance(Class.java:261)
     [java]     at org.apache.jorphan.test.AllTests.main(AllTests.java:194)

If I kill the process, it goes through the same thing -- same output (except for "Test non-headless"), hang at the same point, same stack dump, the only visible difference being the process' command line, which is now:


/usr/local/lib/jdks/j2sdk1.4.2_02/jre/bin/java -classpath /home/jordi/load-test/Eclipse/jakarta-jmeter/lib/Tidy.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/avalon-excalibur-4.1.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/avalon-framework-4.1.4.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/commons-collections.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jakarta-oro-2.0.7.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jdom-b8.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/js.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/junit.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/logkit-1.2.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/soap.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/velocity-1.4-dev.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xalan.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xercesImpl.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/xml-apis.jar:/home/jordi/load-test/Ecl
ipse/jakarta-jmeter/lib/htmlparser.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/jorphan.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/bsf.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_core.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_components.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_functions.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_http.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_ftp.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_jdbc.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_java.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_ldap.jar:/home/jordi/load-test/Eclipse/jakarta-jmeter/lib/ext/ApacheJMeter_tcp.jar org.apache.jorphan.test.AllTests ../lib/ext ./jmetertest.properties org.apache.jmeter.util.JMeterUtils

Comments:
- How is it that the headless run is calling an X11 native method?
- I'm on Linux, so the issue may be Linux-specific.

If I try with gump.run=true, both runs throw a HeadlessException and it does not hang:

test-only:
     [echo] gump.run = true
     [java] setting up logging props using file: ./jmetertest.properties
     [java] Initializing Properties: ./jmetertest.properties
     [java] Setting JMeter home: /home/jordi/load-test/Eclipse/jakarta-jmeter/bin/./..
     [java] java.awt.headless=true
     [java] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
     [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
java/awt/HeadlessException
     [java]     at java.lang.Class.forName0(Native Method)
     [java]     at java.lang.Class.forName(Class.java:115)
     [java]     at org.apache.jorphan.test.AllTests.suite(AllTests.java:275)
     [java]     at org.apache.jorphan.test.AllTests.main(AllTests.java:176)
     [java] Java Result: 1
     [echo] Test non-headless
     [java] setting up logging props using file: ./jmetertest.properties
     [java] Initializing Properties: ./jmetertest.properties
     [java] Setting JMeter home: /home/jordi/load-test/Eclipse/jakarta-jmeter/bin/./..
     [java] java.awt.headless=null
     [java] java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
     [java] Exception in thread "main" java.lang.NoClassDefFoundError: 
java/awt/HeadlessException
     [java]     at java.lang.Class.forName0(Native Method)
     [java]     at java.lang.Class.forName(Class.java:115)
     [java]     at org.apache.jorphan.test.AllTests.suite(AllTests.java:275)
     [java]     at org.apache.jorphan.test.AllTests.main(AllTests.java:176)
     [java] Java Result: 1

Funny....


--
Salut,

Jordi.

En/na BAZLEY, Sebastian ha escrit:
BTW, I'm trying to track down the cause of the GUI errors under Gump, and
the build file now runs the test twice, once headless and once non-headless.
This needs to be removed at some stage.

If it is causing problems, I can refactor to create a test-once target,
leaving Gump to do it twice.

Not sure about a hang, but it can be a bit slow.

S.
-----Original Message-----
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 11:27
To: JMeter Developers List
Subject: Unit tests totally broken


ant test shows one failure more than it used to. In addition, it now hangs. :-(

We must all (including myself) learn to run the tests before checking.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to