node.js - JMeter automatically setting incorrect "Content-Length" header -


i new jmeter , using develop test plan our node/express server. added 2 http requests: 1 add user, , 1 delete user. first request (add user) goes through fine, second request failing. reason failing appears jmeter setting 2 content-length headers onto request - 1 correct , other not. server logs show error:

{ [error: request size did not match content length] type: 'request.size.invalid', message: 'request size did not match content length', statuscode: 400, status: 400, received: 2, expected: 1299, length: 1299 } 

in view results tree, see second request has following headers:

request headers: connection: keep-alive content-type: application/json content-type: application/json; charset=utf-8 date: wed, 30 sep 2015 18:50:17 gmt vary: accept-encoding x-powered-by: express content-length: 1299 connection: content-length: 2 user-agent: apache-httpclient/4.2.6 (java 1.5) 

as can see, jmeter setting 2 content-length headers , cannot figure out why (it should 2 - not sure 1299 coming from). (also noticed it's setting 2 content-type headers well, not sure if related.)

i have googled issue , cannot seem find answers. if has tips or suggestions, appreciated. attaching screenshots of jmeter reference (sensitive information removed). thanks!

http request defaults (server name removed)

http header manager (x-app-id removed)

http request create user

http request delete user

here jmeter logs when run test:

2015/10/02 10:47:21 info  - jmeter.engine.standardjmeterengine: running test! 2015/10/02 10:47:21 info  - jmeter.samplers.sampleevent: list of sample_variables: [] 2015/10/02 10:47:21 info  - jmeter.gui.util.jmetermenubar: setrunning(true,*local*) 2015/10/02 10:47:21 info  - jmeter.engine.standardjmeterengine: starting threadgroup: 1 : thread group 2015/10/02 10:47:21 info  - jmeter.engine.standardjmeterengine: starting 1 threads group thread group. 2015/10/02 10:47:21 info  - jmeter.engine.standardjmeterengine: thread continue on error 2015/10/02 10:47:21 info  - jmeter.threads.threadgroup: starting thread group number 1 threads 1 ramp-up 10 perthread 10000.0 delayedstart=false 2015/10/02 10:47:21 info  - jmeter.threads.threadgroup: started thread group number 1 2015/10/02 10:47:21 info  - jmeter.engine.standardjmeterengine: thread groups have been started 2015/10/02 10:47:21 info  - jmeter.threads.jmeterthread: thread started: thread group 1-1 2015/10/02 10:47:21 info  - jmeter.services.fileserver: stored: /users/ljackson/documents/users.csv 2015/10/02 10:47:22 info  - jmeter.threads.jmeterthread: thread done: thread group 1-1 2015/10/02 10:47:22 info  - jmeter.threads.jmeterthread: thread finished: thread group 1-1 2015/10/02 10:47:22 info  - jmeter.engine.standardjmeterengine: notifying test listeners of end of test 2015/10/02 10:47:22 info  - jmeter.services.fileserver: close: /users/ljackson/documents/users.csv 2015/10/02 10:47:22 info  - jmeter.gui.util.jmetermenubar: setrunning(false,*local*) 


Comments

Popular posts from this blog

1111. appearing after print sequence - php -

java - WARN : org.springframework.web.servlet.PageNotFound - No mapping found for HTTP request with URI [/board/] in DispatcherServlet with name 'appServlet' -

Ruby on Rails, ActiveRecord, Postgres, UTF-8 and ASCII-8BIT encodings -