Closed Sil68 closed 7 years ago
Like I commented in previous your issue the way of cleaning attachments by setting attachment properties to NULL - is incorrect. Try first what happens if you comment out cleaning logic and go straight to attachment setting.
Another thing is that although on the list of attachment content-type the choice is limited, you can still put any content-type you like. Both in UI by typing the desired value, or programmatically.
I'm trying to create a groovy-based pre-processor (JSR223PreProcessor) for *Custom SOAP Sampler plugin, which is intended to cover to following tasks:
After some quite extensive research on the net--I'm completely new to whole groovy, java, jmeter topic--, I managed to assemble the groovy script shown below.
In a previous post I was faced with an issue with BlazeMeter's step-by-step-debugger plugin, which I resolved by not using it. Now another challenge popped into existence.
Executing the test plan results in an error message, reading
Having a peek into the jmeter.log file reveals
Apparently the approach taken to empty the list of currently registered attachments is leading to this kind of error, which now is begging the question as how to implement this is a correct fashion (where are these NUL entries coming from, which are making up apprximately 95% of the whole log file?).
One tackled, another one to go..
My setup comprises:
Sample input csv file
This file is getting read twice: (1) by the JSR223 pre-processor to build the attachment list; (2) by the Custom SOAP Sampler, which subsequently iterates over each entry of this file, and passes the relevant bits & bobs to the SOAP Envelop