On 29 November 2011 08:43, Schweizer, Adrian <[email protected]> wrote: > Both, actually. It doesnt work locally with -n, and it doesnt work on a > remote linux host, that doesnt have a desktop environment.
First you need to find out why it is not working with -n. That will almost certainly fix client-server mode, although there are additional things that can go wrong (e.g. fields that are not serialisable). I assume that this problem only relates to your specific sampler code, and not standard JMeter samplers? If there is the same problem with JMeter samplers, then obviously that needs to be addressed first. Assuming this is not the case, then as I already wrote, your sampler code is probably relying on something in the GUI to set up its variables, rather than using the variables from the test plan At the risk of stating the obvious, add plenty of debug statements to the code so you can track down what is happening. > Also, the only GUI related stuff I can see are the FileEditor and > TextAreaEditor classes which are used in the bean. > > > Am 28.11.2011 um 15:23 schrieb "sebb" <[email protected]>: > >> On 28 November 2011 13:33, Schweizer, Adrian <[email protected]> wrote: >>> It has to be something specific to headless mode, though, because the test >>> works just fine using the GUI. >> >> Do you really mean headless mode, or are you just running the test on >> the same host in non-GUI mode? >> >> They are very different. >> >> Headless is where the host does not support a GUI, and you may have to >> run the test using -Djava.awt.headless=true as well as using "-n" to >> suppress the GUI. >> >> Non-GUI just means running without the JMeter GUI, i.e. using the "-n" >> command-line option. >> >> If your test runs in GUI mode but not in non-GUI mode then there is >> almost certainly a problem with your sampler. >> It's probably relying on the GUI class to do something - but the GUI >> class is not invoked in non-GUI mode. >> >>> >>> Am 28.11.2011 um 13:52 schrieb "sebb" <[email protected]>: >>> >>>> On 28 November 2011 12:42, Schweizer, Adrian <[email protected]> wrote: >>>>> No, there is no error, just the sampler result posted in the last message. >>>> >>>> In that case, I think the problem is in your code, because the 000 >>>> code can only remain if the sample is not successful and did not >>>> trigger one of the existing catch blocks (because these reset the >>>> status) >>>> >>>> Or perhaps no sample was generated - what happens if the loop is not >>>> entered? >>>> >>>>> >>>>> Am 24.11.2011 um 19:50 schrieb "sebb" <[email protected]>: >>>>> >>>>>> On 24 November 2011 16:37, Schweizer, Adrian <[email protected]> wrote: >>>>>>> We previously tried to migrate, but there were strange problems with >>>>>>> the jMeter running on our CI...maybe we'll give it another try. In the >>>>>>> following, the error message and the code of the custom sampler that >>>>>>> produces it, along with a screenshot (attached) of the sampler's >>>>>>> configuration: >>>>>>> >>>>>>> <samplerResult><testsuite>TC008 XML: Automatisch Intervenieren >>>>>>> Import</testsuite><testcase>clean >>>>>>> mailbox</testcase><durationInSeconds>0.062</durationInSeconds><date>24.11.2011 >>>>>>> 16:27:51</date><result><![CDATA[FAILURE >>>>>>> >>>>>>> Response Message: >>>>>>> >>>>>>> Response Data: >>>>>>> >>>>>>> Response Code: 000 >>>>>>> >>>>>>> Response Headers: >>>>>>> >>>>>>> Sampler Data: pop3://[email protected]]]></result></samplerResult> >>>>>>> >>>>>> >>>>>> I'll try and take a look at the code later, but were there any errors >>>>>> in the jmeter.log file? >>>>>> >>>>>> The fact that the response code is set to 000 looks odd, as this >>>>>> suggests the sample failed without invoking any of the catch clauses. >>>>>> >>>>>> The error handling probably needs enhancing - maybe there are some >>>>>> Errors you need to catch? >>>>>> <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
