| Summary: | Variable Listener filenames do not get processed in remote tests | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Oliver Erlewein <olivere> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | ksummerlin, p.mouawad |
| Priority: | P3 | ||
| Version: | 2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
I've had a look at this, and it seems that the problem is that the filename is being retrieved as a StringProperty, rather than a FunctionProperty, so the functions are not being resolved. The test plan is processed OK for function calls that are resolved on the server (e.g. using __time() in test element name works OK), however the Listeners are actually run on the client by RMI calls from the server. It seems that the local (client) part of the test plan is not being processed to resolve function references - however I have not yet found out where this needs to be done. There was a problem with the fix - it was incomplete. Now fixed in SVN r592849. However, it's still not possible to use plain variables in remote test file names. (In reply to comment #3) > There was a problem with the fix - it was incomplete. > Now fixed in SVN r592849. > > However, it's still not possible to use plain variables in remote test file > names. Has no work been done on this recently? I just ran into this error today while doing load tests. As far as I recall, this would be very tricky to resolve, as the variables are defined on the server, but the files are opened by the client. (In reply to comment #5) > As far as I recall, this would be very tricky to resolve, as the variables are > defined on the server, but the files are opened by the client. I'm assuming in reference to my situation where I'm running the test from the GUI you mean the GUI as the client? Just checking to make sure I'm understanding you correctly Also, are there workarounds for this then? (In reply to comment #6) > (In reply to comment #5) > > As far as I recall, this would be very tricky to resolve, as the variables are > > defined on the server, but the files are opened by the client. > > I'm assuming in reference to my situation where I'm running the test from the > GUI you mean the GUI as the client? Just checking to make sure I'm > understanding you correctly Yes, in client-server mode the client is the node that starts the tests on the servers. > Also, are there workarounds for this then? Don't use variables; use properties or functions instead. *** Bug 46779 has been marked as a duplicate of this bug. *** Make it an enhancement but maybe it should be closed as won't fix. Currently possible using Properties not variables. Should be enough. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1901 |
I have a distributed load site with Windows XP PC's running JMeter 2.2. I've written my script to save data to a file (Simple Listener) ./XYZ_${__time(YMDHMS)}.jtl . Now if I run the script locally all's fine and the date gets written. If I use the same script on a remote machine (via RMI) the variable doesn't resolve and the filename is literally ./XYZ_${__time(YMDHMS)}.jtl. Now with times that might be a bit difficult as that changes but even static variables do not get translated.