bug: cached JMS request
I spent a lot of time already tracing and trying to resolve this bug.
issue:
JMS message that is sent via soap request is somehow cached in temporary files and if you happen to change/try to parametize/itterate a different value, keeps sending the original request.
impact:
you have to make one JMS request at a time. cant setup cycle through a parameter. IF you want to make a new JMS request, you have to make a new soap request. Its unpractical.
root cause :
Test consists of a JMS soap request with a String to a MOM que.
the que works, sends a message. However, after you send it, if you try sending a DIFFERENT message, it will still send the original CACHED message. It took a while to figure out what was the source of the problem while testing MOM and finally figured it out it was coming from SOAPUI.
I read server logs and client side soapui logs and I think i see a problem. When running soap testcase it cannot delete temporary files after finishing up. Hense the "cached" request.
My structure of the test is to itterate through groovy about 40-50 vars from a CSV file. It works as long as I create an identical request, brand new soap request, using mom endpoints. The JMS has parameters that are fed through a setup script. Bear in mind for Jenkins its unreasonable to have to create a new request every time you run a test. I have researched a solution and I can probably code up a setup/teardown that in groovy creates a test step and deletes after the run but I really dont want to resort to that.
I have tried 5.2.1 2.0 and 1.3 versions. Also tried redoing my Hermes JMS config as well, clearing cache manually (though /apps/local storage/ temp ....)
I have not seen a single post about this problem.