Hi,
Currently, we are trying to simulate a scenario where we generate a signed SAML 
message, and then send that message (it is encoded) as the BODY in POST request.
So currently in the test plan, we use the OS Process Sampler to run a Java app 
to create (and sign and encode) the SAML message and output that to stdout.  
The Beanshell Post processor captures that output into a Jmeter var, which we 
then use as the BODY Data in an HTTP Request.
As I asked earlier, is there any way to specify how long Jmeter will wait to 
consider the test plan run complete, e.g., we would like to increase to try to 
get more of the requests/responses.
Jim

    On Friday, August 23, 2019, 7:05:33 PM UTC, Ivan Rancati 
<[email protected]> wrote:  
 
 You have an interesting setup: JMeter and Java app (is it part of the
System under test, btw?) on the same computer.

If you can't run JMeter and Java app on two different computers, this might
work:
-Test 1, that runs the Java app, to generate a file with  URLs and/or POST
contents
-Test 2, to run later, reads the above file and tests the web application

Ivan

On Thu, Aug 22, 2019 at 1:30 PM [email protected]
<[email protected]> wrote:

>  Hi,
> Is there a way to increase/set the amount of time that Jmeter will wait
> for more responses, after the scheduler time has elapsed?
> With this test, I think the java app that is run is taking so much
> processor time that the HTTP Requests are not being firede up.
>
> Thanks,Jim
>
>
>
  

Reply via email to