jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hohmann, Kurt D" <>
Subject Application logout failure
Date Thu, 01 Dec 2016 19:42:56 GMT

I'm running into a roadblock on a script I've developed. I'm using the HTTP URL Re-writing
Modifier to read a JSESSIONID after successful login (which is appended to the URL and used
in lieu of a cookie).  I'm also using a Regular Expression Extractor early in the script to
grab a viewstate, which I'm then plugging back in as a variable on all of my POSTS. Everything
seems to work fine until I try to log out.

I'm using Fiddler to compare what's happening when I manually log out vs my JMeter script.
The POST request that submits the logout request has nearly identical request headers (the
only differences are in the user agent (different browsers), cookie (which is ignored by the
server anyway) and referrer parameters (the manual request appends the jsessionid). The post
data for both manual and jmeter are in agreement, but I have the "Use multipart/form-data
for POST" checked in jmeter so there's a significant difference in content length. If I try
unchecking that box, the POST data matches what I see in the manual run but I get a 500 response
from the server.

Using the Results Tree listener, it *looks* like JMeter is successful. However, logout never
actually occurs - I can confirm that by checking the application itself. Also, while the response
headers are exactly the same, the actual response is different:

Successful (manual) response:
<partial-response><redirect url="login.xhtml"></redirect></partial-response>

Unsuccessful (JMeter) response:
<?xml version="1.0" encoding="UTF-8"?><partial-response id="j_id__v_0"><changes><eval><![CDATA[PrimeFaces.ajax.Utils.loadStylesheets(['/javax.faces.resource/components.css.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/scrollpanel/scrollpanel.css.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/fileupload/fileupload.css.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/styles.css.xhtml?ln=css']);PrimeFaces.ajax.Utils.loadScripts(['/javax.faces.resource/jquery/jquery.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/core.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/components.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/jquery/jquery-plugins.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/scrollpanel/scrollpanel.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/printer/printer.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/fileupload/fileupload.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/hotkey/hotkey.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/idlemonitor/idlemonitor.js.xhtml?ln=primefaces&v=6.0','/javax.faces.resource/jsf.js.xhtml?ln=javax.faces']);]]></eval><update

If anyone has any thoughts about how I might further troubleshoot this issue, I'd love to
hear them. Note that I've tried tailing the Apache logs on the web server, but I'm not seeing
a significant difference there.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message