On 16/02/2009, Noel O'Brien <[email protected]> wrote: > Hi All, > > The web application I'm testing uses JMS queues for communicating externally > when certain events occur. The JMS point to point sampler in JMeter only > provides for Request and Request/Response tests, however almost all of the > messaging I will be testing will be driven by a HTTP request, i.e. make a > HTTP request and there should be a corresponding message on a JMS queue. > > What is the best way to (at least) functionally test this? I was thinking of > writing a JMS Assertion that I could add to the HTTP Request sampler, does > that sound reasonable? The JMS message occurs as a result of the HTTP request > being made so to me it makes sense for it to be an assertion.
Is the JMS message sent before the HTTP response is returned? Can one guarantee this? I thought JMS was asynchronous. I would expect the HTTP Response Assertion to be used for checking that the HTTP response is OK, i.e. the page contains "message sent OK" or whatever. > Is there any other way of having a "Response" only JMS sampler? I've never used JMS, but isn't that what JMS Subscriber does? i.e what does the intended JMS recipient do? > Regards, > Noel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
