Service Virtualization

I have a requirement where I need to extract values from DB result and store them in properties.

I'm adding about 400 filters. But when I ran it, I get an exception as follows:

----------------------------------------------------------------------------

Is there a way to increase this limit?

If not, then how can i achieve this?

J_NeSmith

monika_mehta

Deleted User

VenkatYedidaSyntel

VenkatYedidaCG

Hi,

     Add a "Do Nothing" step and split the number of filters on each step to be less than 100.

Vish 

Thanks!

I feel so dumb not having thought about it...

Hi Mallik,

If by this "I have a requirement where I need to extract values from DB result and store them in properties" you mean that you will take out some data out of DB(from a particular column) and then rest of the filters will be on that data (whatever you have filtered out from that particular column), then this approach of having multiple "Do nothing" steps will work.

But, if your Table has 400 columns and you want to extract all the 400 column's data in separate properties, then you will have to have 4 DB steps(with same query, of-course) with 100 filters each. I don't know of any filter which straight away stores the entire row returned by the JDBC step otherwise this scenario also would have worked with the "Do Nothing" steps approach.

Correct me if I am wrong. MarcyNunns

Thanks

Curious thought...  Could you use a Read Rows from JDBC Table dataset and allow DevTest to automatically create the filter(s) based on the column names returned by the query?

I am uncertain if there is a DT limitation on the number of filters or not -- 400 is a reasonably large number of columns for a query result.  Using a dataset will also provide the capability to iterate over the result set if more than one row is returned which may or may not be a requirement.

Hi Joe,

Thanks for your response. Actually I'm selecting four columns in the table and I'm looking to get 100 rows in the resultset. So 4 columns x 100 rows = 400 properties. I want to create all these properties in the DB query step and use them in the following XML request.

Reply by Rahul Verma is more of what I wanted.

Thanks much.

ShubhamAryaMallikarjunMelagiri 

Please check if setting up below configuration properties lisa.prop files helps.

lisa.numFilters.warning=100

lisa.numAsserts.warning=100

Awesome!

This is what I was actually looking for.

Thanks much.