Hi Jeff,
The snippets of code you post look correct. So, not sure where it the hiccup.
I personally always try to use existing filters, assertions, etc... So my suggestion would be to use a Request Data Copier DPH and copy the incoming metadata to properties. That “should” always work. If in the RDC DPH you use “request” as prefix (which I recommend) then the property to use in the JDBC step would be {{request_HTTP-URI}}
If you want to pursue the scriptable DPH route then I try to assess before the JDBC step that this property URI actually exists, then at least you know if the issue is in the DPH or in the JDBC step.
Easiest is to debug your VSM in the workstation ITR, and look in the properties tab. Or e.g. as a last statement of your DPH add something like System.out.println(“+++ URI = “ + testExec.getStateValue(“URI”)); and then look in the workstation log or in the VSE log for this line.
Cheers,
Danny